-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Timeouts on ARM64 Linux Cavium #52589
Comments
Seems like another reason to migrate to GCE instances |
This started since 87362c6 which greatly decreased timeouts on arm and arm64. |
I would give up service tests on Linux ARM64 to get testing at all going on Windows ARM64. |
Several tests seems to be just at the current timeout threshold and flaking between timeout and their normal outcome. Cf. 87362c6 Bug: #52589 Change-Id: I4e89aa71618c51a9ca1d38e8d03fffbcd919a744 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/307972 Reviewed-by: Alexander Thomas <athom@google.com> Commit-Queue: Ryan Macnak <rmacnak@google.com>
I'm reapproving:
|
Reapproving
|
Reapproved: ✔ service/dds_disconnects_existing_clients_test/dds And also ✔ service/collect_all_garbage_test/dds This is getting rather labor intensive.
@bkonyi thoughts? |
Reapproved:
|
Reapproving:
|
The timeout multipiler for linux-arm64 was originally 4, then lowered to 1 (see [0]), then increased again to 2 (see [1]). Though it seems that service tests are still flakily timing out, so let's try restoring the original multilier. [0] https://dart-review.googlesource.com/c/sdk/+/306662 [1] https://dart-review.googlesource.com/c/sdk/+/307972 Also special case `ia32` in timeout calculations due to not using an AppJIT trained `kernel-isolate` snapshot and therefore being very slow, especially in ia32-debug mode. Issue #52589 TEST=ci Change-Id: Iab8c768866aec9e77bb83c7a3242cc5de8fb4e2f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/312905 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Slava Egorov <vegorov@google.com>
@mkustermann I had to reapprove this timeout again, even though you just increased the timeout multiplier. Thoughts? |
Here's the impact of my daa35fd that restored the timeout multiplier for => I suspect the majority of the flaky timeouts are gone now for |
reapproving service/process_service_test/service, service/set_library_debuggable_test/dds, and service/regress_28443_test/dds https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/vm-linux-release-arm64/732/overview |
Bug: #52589 Bug: #53138 Change-Id: Iaf6e499d80726b5ec8a810a5d3bd1d90a0d93af9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/318800 Commit-Queue: Ryan Macnak <rmacnak@google.com> Reviewed-by: Alexander Aprelev <aam@google.com>
In particular, this un-skips the service tests. TEST=ci Bug: b/302156166 Bug: #26109 Bug: #27806 Bug: #33057 Bug: #52589 Change-Id: Ieddf50ac6c27d23c5efa26a7e5bf7f9044350a5e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/328381 Reviewed-by: Jonas Termansen <sortie@google.com> Commit-Queue: Ryan Macnak <rmacnak@google.com>
Bug: b/302156166 Bug: #52589 Change-Id: I9470dc13d3f41bf7f5e77c4168efeec7d17e9263 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/329564 Reviewed-by: Jonas Termansen <sortie@google.com> Reviewed-by: Alexander Thomas <athom@google.com> Commit-Queue: Ryan Macnak <rmacnak@google.com>
There are new test failures on [test] Don't apply simulator timeout multipler to ARM hardware..
The tests
are failing on configurations
The text was updated successfully, but these errors were encountered: