Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bazel CI] Test failure gopackagesdriver_test with Bazel@HEAD in CI #3889

Closed
sgowroji opened this issue Mar 15, 2024 · 4 comments · Fixed by #3893
Closed

[Bazel CI] Test failure gopackagesdriver_test with Bazel@HEAD in CI #3889

sgowroji opened this issue Mar 15, 2024 · 4 comments · Fixed by #3893

Comments

@sgowroji
Copy link
Contributor

sgowroji commented Mar 15, 2024

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3720#018e4049-fb9b-4c0e-8f91-652ef7e9416f

Platform: MacOS, Windows, Ubuntu

Logs:

FAIL: �[0m//go/tools/gopackagesdriver:gopackagesdriver_test (Exit 1) (see /private/var/tmp/_bazel_buildkite/3e69e71b71ef10f5180eefcc51399150/execroot/io_bazel_rules_go/bazel-out/darwin_x86_64-fastbuild/testlogs/go/tools/gopackagesdriver/gopackagesdriver_test/test_attempts/attempt_1.log)

Culprit:

Steps:

 git clone https://github.com/bazelbuild/rules_go
git reset 7538c5438308e86ab6ece6692847226cd8c9fda6  --hard
export USE_BAZEL_VERSION=6f254ce0f95d70e744b513a94d577036712befac
bazel test //... 

CC Greenteam @Wyverald

@fmeum
Copy link
Member

fmeum commented Mar 15, 2024

@jayconrod It seems more likely that this is caused by 7538c54 then by a Bazel commit (I checked the history and nothing stood out). I can also look into it though.

@jayconrod
Copy link
Contributor

I'll try to reproduce the issue today and figure out what's going on.

@fmeum
Copy link
Member

fmeum commented Mar 15, 2024

I'll try to reproduce the issue today and figure out what's going on.

Wild guess: Bazel@HEAD returns a fixed non-semver version string, which may throw off the feature detection.

@jayconrod
Copy link
Contributor

@fmeum You were exactly right. It returns development version. The surprising thing was that we assume that means 6.0.0. #3893 should fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants