Skip to content

slurmprocessor: update collector dependencies to v0.153.0#152

Merged
tooji merged 1 commit into
facebookresearch:mainfrom
sdmcclain:slurmprocessor-otel-0.153
Jun 4, 2026
Merged

slurmprocessor: update collector dependencies to v0.153.0#152
tooji merged 1 commit into
facebookresearch:mainfrom
sdmcclain:slurmprocessor-otel-0.153

Conversation

@sdmcclain

Copy link
Copy Markdown
Contributor

Summary

Update the slurmprocessor module's OpenTelemetry Collector library dependencies (go.opentelemetry.io/collector/*) from 0.126.0 / 1.32.0 to 0.153.0 (beta) / 1.59.0 (stable), and the go directive to 1.26.0.

At the previous pin, go mod tidy fails resolving go.opentelemetry.io/otel/sdk/internal/internaltest, a transitive test package the current otel-go no longer provides. The 0.153.0 dependency set is self-consistent and resolves cleanly.

No processor source changes were required; the component/processor/pdata APIs the processor uses are unchanged across these versions. The only code change is in the test: config_test.go used the collector's internal service/internal/testcomponents package (not importable across module boundaries) and now uses the public otelcoltest.NopFactories(), with testdata/config.yaml switched to the nop receiver/exporter to match.

Test Plan

go mod tidy
go build ./...
go vet ./...
go test ./...
ok  	github.com/facebookresearch/gcm/slurmprocessor	0.012s

Update the slurmprocessor module's OpenTelemetry Collector library
dependencies (go.opentelemetry.io/collector/*) from 0.126.0 / 1.32.0 to
0.153.0 (beta) / 1.59.0 (stable), and the go directive to 1.26.0.

At the previous pin, `go mod tidy` fails resolving
go.opentelemetry.io/otel/sdk/internal/internaltest, a transitive test
package the current otel-go no longer provides. The 0.153.0 dependency
set is self-consistent and resolves cleanly.

No processor source changes were required; the component/processor/pdata
APIs the processor uses are unchanged across these versions. The only
code change is in the test: config_test.go used the collector's internal
service/internal/testcomponents package (not importable across module
boundaries) and now uses the public otelcoltest.NopFactories(), with
testdata/config.yaml switched to the nop receiver/exporter to match.

Verified: go mod tidy, go build ./..., go vet ./..., go test ./... pass.
@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

CI Commands

The following CI workflows run automatically on every push and pull request:

Workflow What it runs
GPU Cluster Monitoring Python CI lint, tests, typecheck, format, deb build, pyoxidizer builds
Go packages CI shelper tests, format, lint

The following commands can be used by maintainers to trigger additional tests that require access to secrets:

Command Description Requires approval?
/metaci tests Runs Meta internal integration tests (pytest) Yes — a maintainer must trigger the command and approve the deployment request
/metaci integration tests Same as above (alias) Yes

Note: Only repository maintainers (OWNER association) can trigger /metaci commands. After commenting the command, a maintainer must also navigate to the Actions tab and approve the deployment to the graph-api-access environment before the jobs will run. See the approval guidelines for what to approve or reject.

@tooji tooji merged commit e0d2d03 into facebookresearch:main Jun 4, 2026
35 checks passed
@meta-codesync

meta-codesync Bot commented Jun 4, 2026

Copy link
Copy Markdown

@tooji has imported this pull request. If you are a Meta employee, you can view this in D107542218.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants