-
Notifications
You must be signed in to change notification settings - Fork 139
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
Permission denied on Windows tests (flaky) #1012
Comments
I can reproduce this issue locally, will look into it soon! |
It looks like we are hitting something similar to bazelbuild/bazel#7458 I haven't figured out exactly why, |
OK, the reason of this failure is because the Java worker will hold the file handle of To workaround this issue on CI, we can use Bazelisk's |
It still fails: https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/592#83a2bd3b-a04d-4dea-8aa1-3812ec39c251
|
Can we reopen this bug? Or I can file a new one. |
Oh sorry, we can re-open this. Looks like my change only fixed the Bazel Federation case, but not for this one. |
If some directory is set to read-only on Windows, DeletePath will fail to delete that directory even when no one else is using it. Previously, we only remote read-only attribute for files before deleting, we should also do the same for deleting directory. Fixes bazelbuild/continuous-integration#1012
The bug is on Bazel side. Can you please help review the fix bazelbuild/bazel#11982? |
Let's keep this open until we are sure the problem is fixed. We'll have to wait for the next month's Bazel release. |
FYI, I'm hitting this in Stardoc today with Bazel 6.3.2 as well as 7.0 pre: bazelbuild/stardoc#179 -> https://buildkite.com/bazel/stardoc/builds/1081 |
…t_transitions (#179) And to make sure we stay unbroken, add the flag to our ci config - which on Windows requires setting `BAZELISK_SHUTDOWN=1` to work around bazelbuild/continuous-integration#1012 Fixes #145
... and fix Windows CI failure (see bazelbuild/continuous-integration#1012)
FYI: I've been seeing this lately. Mostly with rules_python, but I also so it in a BCR PR today. Not a lot, maybe like once or twice a week / 50-100 CI runs. Few enough that pressing retry isn't a big inconvenience, but often enough that retry doesn't always fix it, and enough to mention it. |
I see lots of Windows failures on this pipeline: https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/579
For example, I see 7 failures for the flag
incompatible_string_replace_count
, all of them seem flaky.Examples of error messages:
The text was updated successfully, but these errors were encountered: