-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Python tests are flaky on Windows #3273
Comments
I added more logging to those tests, will be pushed to GitHub soon. |
Until then, I have no idea what could be going on. |
According to the error messages, Bazel sometimes cannot find VC through registry when running in python tests.
|
This is for debugging #3273 Change-Id: I84e260ae1a22147fed0cffc2960352c77af2cf58 PiperOrigin-RevId: 160399209
http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=windows-x86_64/847/console
But should be:
|
A workaround for #3273 RELNOTES: None PiperOrigin-RevId: 160509802
I don't know why I closed this bug. I still see this problem on my workstation:
I see that 6a4247b removed the |
I removed it because after #2675 is fixed, Bazel should be able to detect VC++ installation on its own. Before that, python_tests were flaky because the result of |
You're right, sorry for the false alarm. My attempts to run the test failed probably because of where my MSYS was installed. |
http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=latest,PLATFORM_NAME=windows-x86_64/843/console
Bazel sometimes exist with exitcode = 2 unexpectedly
//cc @laszlocsomor Any idea?
The text was updated successfully, but these errors were encountered: