Closed Bug 1775683 Opened 3 years ago Closed 2 years ago

Intermittent accessible/tests/browser/e10s/browser_caching_name.js | single tracking bug

Categories

(Core :: Disability Access APIs, defect, P3)

Product:
Core
Component:
Disability Access APIs
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
121 Branch
Tracking Flags:
Tracking Status
firefox121 --- fixed

People

(Reporter: jmaher, Assigned: Jamie)

References

Details

(Keywords: intermittent-failure, intermittent-testcase)

Attachments

(1 file)

Bug 1775683: Request a longer timeout for accessible/tests/browser/e10s/browser_caching_name.js.
48 bytes, text/x-phabricator-request
Details | Review
No description provided.

Additional information about this bug failures and frequency patterns can be found by running: ./mach test-info failure-report --bug 1775683

Severity: -- → S4

Looking at recent failures here, it looks like there are two distinct issues:
(1) Windows failures like this:

TEST-UNEXPECTED-FAIL | accessible/tests/browser/e10s/browser_caching_name.js | Wrong name of the accessible for [DOM node id: btn, role: pushbutton, name: 'do not press me', address: [xpconnect wrapped nsIAccessible]] - Got "do not press me", expected "press me"

(2) Linux tsan failures like this:

TEST-UNEXPECTED-FAIL | accessible/tests/browser/e10s/browser_caching_name.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort.
TEST-OK | accessible/tests/browser/e10s/browser_caching_name.js | took 122508ms

Not sure about (1), but for (2) -- the Linux TSAN ones --- those don't look like they're hanging or anything; the test is just still running checks up to the moment that we overshoot the timeout threshold. This is likely just slowness from the TSAN overhead. The duration (122,000ms == 2 minutes) is fairly long, but believable (i.e. not necessarily pathological).

We should probably just use requestLongerTimeout(2) to double the timeout threshold here, at least on Linux, since the signal-to-noise for this test overshooting the threshold right now is just noise.

Morgan, see comment 55 - could you add SimpleTest.requestLongerTimeout(2) to the start of this a11y mochitest, if that looks OK to you?

(Based on the most recent comment here, nearly all of the intermittent failures are still TSAN-specific which means they're probably category-(2) from comment 55.)

Flags: needinfo?(mreschenberg)

Morgan is on PTO. Taking.

Assignee: nobody → jteh
Flags: needinfo?(mreschenberg)

These timeouts are most likely due to slowness from TSAN overhead.

Pushed by jteh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/103c13ea4383 Request a longer timeout for accessible/tests/browser/e10s/browser_caching_name.js. r=eeejay

https://hg.mozilla.org/mozilla-central/rev/103c13ea4383

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox121: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: