unit_tests on Android device Nexus 5X failing on chromium.memory/Android CFI |
|||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of xiaochengh@chromium.org unit_tests on Android device Nexus 5X failing on chromium.memory/Android CFI Builders failed on: - Android CFI: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Android%20CFI
,
Jul 17
New timeouts seen in build 2108 and 2109
,
Jul 17
,
Jul 17
The shards in unit_tests each seem to run for about 8-12 minutes, with the absolute execution timeout set to 15 min. My guess is that occasionally something slows it down a bit (nondeterministically), and the shard times out. I don't think we can reasonably expect devices to have a stable runtime performance, so this variance is likely expected. Perhaps, a reasonable solution to this is to increase sharding, or increase the timeout. +jbudorick and bpastene for an opinion on this. I can update the configs.
,
Jul 17
See also issue 795428 - possibly related.
,
Jul 17
Also seen on android-mashmallow-arm64-rel: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel
,
Jul 20
#4: Note that thakis pulled all of the android-specific hard timeouts in https://chromium-review.googlesource.com/c/chromium/src/+/1143694. #6: in general, if you're citing something from a builder, please link a specific build -- the context can get lost pretty quickly if you only link a builder.
,
Jul 24
Thanks! That's good to know (about removing the timeouts). Looking through the latest builds in https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Android%20CFI, I cannot see any failures due to timeouts anymore. Similarly, spot-checking a few failed builds in https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel doesn't show any timeouts. I'm going to close this bug as fixed by that CL in #7. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xiaoche...@chromium.org
, Jul 17