ci: fix CI failures (gvm v0.6.0 + skip broken cgroup tests)#273
Merged
orestisfl merged 15 commits intoelastic:mainfrom Dec 11, 2025
Merged
ci: fix CI failures (gvm v0.6.0 + skip broken cgroup tests)#273orestisfl merged 15 commits intoelastic:mainfrom
orestisfl merged 15 commits intoelastic:mainfrom
Conversation
The CI builds were failing with HTTP 403 errors when downloading Go: gvm: error: failed downloading from https://storage.googleapis.com/golang/go1.24.7.windows-amd64.zip: download failed with http status 403 See andrewkroh/gvm#117 that describes the issue on gvm's side. Tested locally: $ /tmp/gvm-0.6.0 --version 0.6.0 $ eval "$(/tmp/gvm-0.6.0 1.24.7)" && go version go version go1.24.7 linux/amd64 Updated gvm version in: - .buildkite/pipeline.yml (SETUP_GVM_VERSION env var) - .buildkite/scripts/run-win-tests.ps1 (hardcoded URL) This aligns with the beats repository configuration.
mauri870
reviewed
Dec 10, 2025
|
Good catch for the gvm version, I did it on Beats and Ingest-dev but didn't think about here!! |
mauri870
reviewed
Dec 10, 2025
elastic-agent-system-metrics_build_862_container-system-tests-rhel-9.log
Outdated
Show resolved
Hide resolved
mauri870
approved these changes
Dec 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR fixes multiple CI failures:
1. Update gvm to v0.6.0 (fixes Go download 403 errors)
The CI builds were failing with HTTP 403 errors when downloading Go:
gvm v0.6.0 migrated to the official Go downloads API at
go.dev/dl.See: andrewkroh/gvm#117
Updated gvm version in:
.buildkite/pipeline.yml(SETUP_GVM_VERSION env var).buildkite/scripts/run-win-tests.ps1(hardcoded URL)Tested locally:
This aligns with the beats repository configuration.
2. Skip flaky cgroup tests (issue #270)
Container tests fail when cgroups are unavailable due to:
/../..which can't be resolvedThese are treated as non-fatal errors in production code. Our testing suite was designed to predict exactly when these failures are going to happen but something has gone wrong in the meantime, more investigation is needed.
Changes:
stats.Cgroup == nilinTestContainerMonitoringFromInsideContainerandTestSelfMonitoringFromInsideContainerCGROUPNSMODEenv var from test framework to inner testsvalidateProcResultwhencgroupNSMode == "host" && userID == 0FatalLogMessagescheckVerbosefield witht.Logf), go automatically prints logs with -v or on failure.validateProcResult. The function does not fail immediately anymore and keeps going to maximize failing test's context.Why is it important?
CI is completely broken - no PRs can be merged.
Checklist
I have added an entry inCHANGELOG.md