Closed sgowroji closed 1 month ago
The same failure happens on release Bazel (https://buildkite.com/bazel/bazel-bazel-examples/builds/2766#018e2acf-d2b3-4ad7-88ae-e73c3f46c796), so I think we should just move this issue to the Bazel examples repo? also cc @alexeagle
sorry, I didn't realize we were already in the examples repo...
sorry, I didn't realize we were already in the examples repo...
Np! ;D
@alexeagle Any idea on how to address this flaky failure?
@gregmagolan and @tjgq have had an email thread about it. I think it's a matter of finding some time for it. Our clients observe it sometimes too, we are just having trouble understanding the cause.
Hi Team, Any Update/progress on the above issue ?
1.40.0 rules_js release has a fix/work-around for the issue for most cases. See the PR summary of https://github.com/aspect-build/rules_js/pull/1538 for more info.
I'm pretty sure this is caused by a race in skymeld that isn't related to caching and can't be worked around reliably: https://github.com/bazelbuild/bazel/issues/22073
@alexeagle Did you mean to close this with #445?
Yes, that change includes the version bump for rules_js that @gregmagolan mentioned 4d ago
Yes, that change includes the version bump for rules_js that @gregmagolan mentioned 4d ago
Based on https://github.com/bazelbuild/bazel/issues/22073, I don't think that this can be worked around reliably on the ruleset side, it appears to be an honest race in Skymeld that can affect virtually any external repo. I would suggest keeping this open until it doesn't reproduce in CI anymore.
Okay sure, but does that "honest race in Skymeld" have an owner? I don't think Greg or I are planning to do more here, and I don't love having an issue "rules_js is broken" on the examples repo.
As far as I know @joeleba is actively working on https://github.com/bazelbuild/bazel/issues/22073.
CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3711#018e2bad-eced-489f-aa96-d3974826f324
Platform: MacOS
Logs:
Culprit:
Steps:
CC Greenteam @wyverald