Perma all Android 7.0 test tasks fail with exceptions with "INTERMITTENT_TASK" after multiple retries
Categories
(Firefox Build System :: Task Configuration, defect)
Tracking
(firefox120 fixed, firefox121 fixed, firefox122 fixed)
People
(Reporter: NarcisB, Assigned: bhearsum)
References
Details
(Whiteboard: [stockwell disable-recommended])
Attachments
(1 file)
Live_backing.log: https://firefoxci.taskcluster-artifacts.net/V40nJfjUQ_WYzYEJIlBQsg/5/public/logs/live_backing.log
TH: https://treeherder.mozilla.org/jobs?repo=mozilla-beta&selectedTaskRun=V40nJfjUQ_WYzYEJIlBQsg.5&fromchange=889c2b945041a3cdfba4f89a49812c637bb8cbe9&searchStr=android%2C7.0%2Cx86-64%2Cwebrender%2Cdebug-isolated-process%2Ctest-android-em-7.0-x86_64-qr%2Fdebug-isolated-process-geckoview-gtest-1proc%2Cgtest-1proc
Updated•9 months ago
|
Comment 2•9 months ago
•
|
||
The emulator is failing to start.
Screenshot artifacts for the failed tasks show an emulator pop-up: title="Emulator Running in Nested Virtualization", body="The emulator is running using nested virtualization. This is not recommended. It may not work at all. And typically the performance is not quite good.", check-box="Never show this again." (unchecked).
Comment 3•9 months ago
|
||
It's unclear if this is actually related to bug 1868680, but the recent failures seem coincidental.
Comment 4•9 months ago
|
||
Queue referenced: gecko-t/t-linux-kvm-gcp
No changes have been made to the image used by this queue recently.
Comment 5•9 months ago
|
||
Recent (yesterday's) successful android-em test tasks have emulator logs that show:
Android emulator version 32.1.15.0 (build_id 10696886) (CL:N/A)
The failing tasks' emulator logs have:
Android emulator version 33.1.23.0 (build_id 11150993) (CL:N/A)
Assignee | ||
Comment 6•9 months ago
|
||
This is not really the best fix - ultimately the pinned version should go in a task definition somewhere, I think, and we should even consider pinning in https://searchfox.org/mozilla-central/source/python/mozboot/mozboot/android.py and pinning for even non-Taskcluster users (as we do for the NDK, cmdline tools, etc.)
But this is the safest, quickest fix for the immediate term.
Updated•9 months ago
|
Comment 7•9 months ago
•
|
||
The warning in comment 2 has been in the emulator for a long time...I don't know why it is popping up for us now in this version.
The emulator even has an override for that warning: --no-nested-warnings
. Trying to determine if that helps...
Pushed by nfay@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6f5601bcf5ef pin android emulator version in toolchain tasks r=gbrown! CLOSED TREE
Comment 11•9 months ago
|
||
bugherder |
Comment 12•9 months ago
|
||
The issue is still lingering around on Android 7 TV-nofis as seen here
Updated•9 months ago
|
Updated•9 months ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 15•9 months ago
|
||
(In reply to Norisz Fay [:noriszfay] from comment #12)
The issue is still lingering around on Android 7 TV-nofis as seen here
Most android-em tests use the android-emulator-linux artifact - https://searchfox.org/mozilla-central/rev/c003be8b9727672e7d30972983b375f4c200233f/taskcluster/ci/test/mochitest.yml#188 - but test-verify uses android-sdk-linux - https://searchfox.org/mozilla-central/rev/c003be8b9727672e7d30972983b375f4c200233f/taskcluster/ci/test/misc.yml#124. I doubt there's a good reason for that: test-verify should use android-emulator-linux as well. I'll see if that works...
Comment hidden (Intermittent Failures Robot) |
Comment 17•9 months ago
|
||
(In reply to Norisz Fay [:noriszfay] from comment #12)
The issue is still lingering around on Android 7 TV-nofis as seen
This should be fixed by bug 1869220.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Description
•