-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[Bazel CI] Tests are slow and flaky on macOS arm64 #23726
Comments
Seeing |
@fweikert Do you know if there is any potential infrastructure change that could cause this? |
Before: ``` //src/test/shell/bazel:bazel_java_test (cached) PASSED in 746.9s //src/test/shell/bazel:bazel_java_test_jdk11_toolchain_head (cached) PASSED in 307.3s //src/test/shell/bazel:bazel_java_test_jdk17_toolchain_head (cached) PASSED in 370.7s //src/test/shell/bazel:bazel_java_test_jdk21_toolchain_head (cached) PASSED in 340.6s //src/test/shell/bazel:bazel_proto_library_test (cached) PASSED in 709.5s ``` After: ``` //src/test/shell/bazel:bazel_java_test PASSED in 340.3s //src/test/shell/bazel:bazel_java_test_jdk11_toolchain_head PASSED in 221.2s //src/test/shell/bazel:bazel_java_test_jdk17_toolchain_head PASSED in 218.0s //src/test/shell/bazel:bazel_java_test_jdk21_toolchain_head PASSED in 315.0s //src/test/shell/bazel:bazel_proto_library_test PASSED in 312.3s ``` Related: #23726 PiperOrigin-RevId: 678209188 Change-Id: I3b51584ba2893fe01a7ac084c99961623f0e4b02
Mitigating #23726 PiperOrigin-RevId: 678213406 Change-Id: I99ea19f3dcf56a359e39274ce9043a6b4f64b6a4
The issue seems to be reproducible on some VMs, so it might be related to some infra issue. |
Those tests can sometimes take up to 1h to run for some reason. Disable them in presubmit and we can still monitor them in postsubmit. Related #23726 PiperOrigin-RevId: 678608123 Change-Id: I783e1ba7b09855ee773ea066b8b49f1b36975a3b
Mitigating #23726 PiperOrigin-RevId: 678213406 Change-Id: I99ea19f3dcf56a359e39274ce9043a6b4f64b6a4 Backporting 355b000#diff-544556920c45b42cbfe40159b082ce8af6bd929e492d076769226265f215832fR85
First appearance seems to be: f64cdea at it's parent commit: |
Found an even earlier flaky build: https://buildkite.com/bazel/google-bazel-presubmit/builds/84128 which might rule out f64cdea |
Mitigating #23726 PiperOrigin-RevId: 678213406 Change-Id: I99ea19f3dcf56a359e39274ce9043a6b4f64b6a4 Backporting 355b000#diff-544556920c45b42cbfe40159b082ce8af6bd929e492d076769226265f215832fR85
Do any of these fixes need to be cherry-picked back to 7.4.0 and/or 8.0.0? |
efa0303 should be backported to 8.0.0 |
@bazel-io fork 8.0.0 |
Tests on macOS arm64 should be much more stable after bumping VM specs. Also bumped the size of disk_cache_test as it sometimes timeout on Linux. Closes bazelbuild#23726 PiperOrigin-RevId: 684412631 Change-Id: I5485f839aee0c3a1012196c6628eda9535985b82
Tests on macOS arm64 should be much more stable after bumping VM specs. Also bumped the size of disk_cache_test as it sometimes timeout on Linux. Closes #23726 PiperOrigin-RevId: 684412631 Change-Id: I5485f839aee0c3a1012196c6628eda9535985b82 Commit efa0303 Co-authored-by: Googler <pcloudy@google.com>
A fix for this issue has been included in Bazel 8.0.0 RC2. Please test out the release candidate and report any issues as soon as possible. |
//src/test/shell/bazel:bazel_bootstrap_distfile_tar_test
and//src/test/shell/bazel:bazel_determinism_test
are extremely slow:https://buildkite.com/bazel/google-bazel-presubmit/builds/84154#01922292-cca6-4e56-939b-05a5c7b59da1
Flaky tests are very frequent:
https://buildkite.com/bazel/google-bazel-presubmit/builds/84157#019222c1-653c-4a75-bdf7-7f76d5937946
The text was updated successfully, but these errors were encountered: