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
ctx.split_attr broken nondeterministically with Starlark transitions #8633
Comments
ctx.split_attr also automatically keys on cpu which means it doesn't return the right mapping for transitions keyed on anything else and can throw IllegalStateExceptions. Unfortauntely I'm just now finding this issue though it seems to have been broken forever. 49862c5 puts a bandaid on the issue by just disallowing ctx.split_attr to include starlark transitioned attrs while we work on fixing this. |
I don't think we should delay (again) the release for this, unless it worked with Bazel 0.26. |
I get that. The only reason I ask is because it can lead to hard bazel crashes which I thought upped the priority level of bugs. But I leave the decision up to you as release manager! |
…ss issues are fixed. bazelbuild/bazel#8633 for details RELNOTES: None PiperOrigin-RevId: 253268379
…ss issues are fixed. bazelbuild/bazel#8633 for details RELNOTES: None PiperOrigin-RevId: 253268379
…ss issues are fixed. bazelbuild/bazel#8633 for details RELNOTES: None PiperOrigin-RevId: 253268379
…ss issues are fixed. bazelbuild/bazel#8633 for details RELNOTES: None PiperOrigin-RevId: 253270996
@juliexxia, please update or close this issue. |
This issue seems like it watch band-aid-ed when it first came up (which has definitely been released in Bazel by now) and it's full functionality with a fix will be released soon! |
ctx.split_attr builds itself for every starlark rule, encompassing every attribute with a split transition. In doing so it actually applies transition but doesn't do any of the set up or tear down work necessary for starlark transitions to properly be applied.
The text was updated successfully, but these errors were encountered: