rules_go: ERROR FAILED: //tests/core/transition:hermeticity_test with Bazel@HEAD in Downstream CI
Platform: Windows, MacOs, Ububtu
Logs :
FAIL: //tests/core/transition:hermeticity_test
Steps:
git clone https://github.com/bazelbuild/rules_go.git
git reset 9d5416bcc9d48da3735b73fb5540b1cdbd470b85 --hard
export USE_BAZEL_VERSION=211fd6c14bef2f656265b3d3eb98a476f02ebf88
bazel build //...
Reference issue, which is causing error : https://github.com/bazelbuild/bazel/commit/cb558978820b1fb9b579d8e9578cbb9ca590fe60
CC Green Team @ fweikert
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 19 (7 by maintainers)
Commits related to this issue
- Automated rollback of commit 607d0f7335f95aa0ee236ba3c18ce2a232370cdb. *** Reason for rollback *** It changes the output format of --output=jsonproto to ndjson (i.e. which prints out ConfiguredTarge... — committed to bazelbuild/bazel by zhengwei143 a year ago
- Automated rollback of commit 607d0f7335f95aa0ee236ba3c18ce2a232370cdb. *** Reason for rollback *** It changes the output format of --output=jsonproto to ndjson (i.e. which prints out ConfiguredTarge... — committed to bazelbuild/bazel by zhengwei143 a year ago
Since this change may be rolled forward as an incompatible change in the future, I went ahead and updated the usage: https://github.com/bazelbuild/rules_go/pull/3638
@sgowroji Either that or the rollback should fix this for the next downstream run
@sgowroji Both failures should be fixed by https://github.com/bazelbuild/rules_go/pull/3781.
Looks like an instance of https://github.com/bazelbuild/bazel/issues/19823. I will disable Bzlmod for it.
I submitted https://github.com/bazelbuild/rules_go/pull/3623 to fix this separate issue - it is trivial and unrelated.
That looks like a separate issue - this test failure has been failing even after the rollback in https://github.com/bazelbuild/bazel/commit/dba9e43a26d41c2559568e4abfdece57e79de37d (see for example https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3149#01892e86-2c8f-4b6b-ad39-fb36384d135d)
Btw, I’ve reimplemented this in https://github.com/bazelbuild/bazel/commit/aa8835753cbbed5a837fc10a37464ee4a84941ba, and the previous failures seem to be fixed. So this issue should be closed.
I’ve just rolled back the change in https://github.com/bazelbuild/bazel/commit/dba9e43a26d41c2559568e4abfdece57e79de37d which should fix this.
It got the result from https://buildkite.com/bazel/culprit-finder/builds/5736#0188d70d-c9dc-438e-8119-76650a30b54c, which seems to be the same issue reported in https://github.com/bazelbuild/bazel/issues/18666