[Bazel CI] aspect_rules_js no such file error or directory with Bazel@HEAD in CI about examples HOT 13 OPEN

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: bazelbuild/bazel#22073

from examples.

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

from examples.

sorry, I didn't realize we were already in the examples repo...

from examples.

sorry, I didn't realize we were already in the examples repo...

Np! ;D

@alexeagle Any idea on how to address this flaky failure?

from examples.

@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.

from examples.

Hi Team, Any Update/progress on the above issue ?

from examples.

1.40.0 rules_js release has a fix/work-around for the issue for most cases. See the PR summary of aspect-build/rules_js#1538 for more info.

from examples.

@alexeagle Did you mean to close this with #445?

from examples.

Yes, that change includes the version bump for rules_js that @gregmagolan mentioned 4d ago

from examples.

Yes, that change includes the version bump for rules_js that @gregmagolan mentioned 4d ago

Based on bazelbuild/bazel#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.

from examples.

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.

from examples.

As far as I know @joeleba is actively working on bazelbuild/bazel#22073.

from examples.