c-parsons
c-parsons
Pardon my ignorance, but how would the release of Bazel 0.27.0 affect testing rules_go against Bazel@HEAD at various commits? A Bazel release affecting rules_go CI for Bazel@Release would make sense,...
So, this is failed not tied to a release because these tests uses some details about the host machine, particularly it will, in test, run /usr/bin/bazel. I bet that when...
(Also re: reproducing this error, the `--output_user_root=bogus` is also important, because otherwise bazel crashes with a descriptive error. The error is only suppressed if both `HOME` and `--output_user_root` are specified)
It should be P1 because this is a recent regression that results in a crash bug. IIRC we have a Bazel policy that crash bugs are P1 by default, and...
No, you're right to question me making an assertion about policy with "IIRC". Frankly, I can't find the policy, so I'm not sure if I accidentally made it up. If...
It's unclear to me how dadc49e could be causing this failure, both by looking at the failure and looking at the surrounding builds. 1. The commit in question changes cc_shared_library...
Indeed, the second culprit finder still points to that commit. Would be interested in the results of your bisect. Sorry, it's been a bit of a day with unrelated issues....
I'm having issues getting even a clean build passing with tensorflow, either at HEAD or at https://github.com/tensorflow/tensorflow/commit/007f31c872c9c74f1298b7389d324e3947ede5ce (with bazel 5.3.1) :\ In both cases: ``` bazel build -c opt --output_filter=^$...
Thanks a bunch! Have reproed the error successfully. Still don't have any leads on the underlying failure -- it may take me a bit.