1899777 - TV (--verify) of xpcshell tests times out on Android after 300 seconds due to MOZ_CHAOSMODE=0xfb

Status: RESOLVED FIXED

(Testing :: XPCShell Harness, defect, P2)

Description

[Rob Wu [:robwu]]

While investigating a TV failure on Android (bug 1881876), I discovered that the failure is due to MOZ_CHAOSMODE=0xfb.
According to the live.log in bug 1881876, a typical execution takes 18 - 29 seconds.
When run with MOZ_CHAOSMODE=0xfb, the test times out after 7:29 minutes.
This increased execution time by MOZ_CHAOSMODE looks excessive. Is there a way to reduce the slowdown, and if not, then we should bump the timeout.

Extra info:
After trying all combinations of ChaosMode, I found that this slowdown is caused by the TaskDispatching (0x40) and TaskRunning (0x80) parts. When I run a test without these two (0xfb & ~0x40 & ~0x80 = 0x3b), then the test has the usual execution time:

./mach test toolkit/components/extensions/test/xpcshell/test_ext_scripting_persistAcrossSessions.js --sequential --log-mach-verbose --no-install --setenv=MOZ_CHAOSMODE=0x3b

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:jmaher, could you have a look please?

For more information, please visit BugBot documentation.

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: Bug 1899777 - Adjust CHAOSMODE flags on xpcshell when running test-verify on android. r=gbrown

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ef7bdd0ea0b2
Adjust CHAOSMODE flags on xpcshell when running test-verify on android. r=gbrown

Comment 4

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/ef7bdd0ea0b2