Closed Bug 1819799 Opened 2 years ago Closed 2 years ago

[CTW] untilCacheCondition should treat timeout as a test failure

Categories

(Core :: Disability Access APIs, task)

task

Tracking

()

RESOLVED FIXED
112 Branch
Tracking Status
firefox112 --- fixed

People

(Reporter: Jamie, Assigned: Jamie)

References

Details

Attachments

(1 file)

In a11y browser tests, untilCacheCondition first checks the condition immediately. If the condition isn't met, it waits for a cache update (via an XPCOM observer topic) and tries again. If it doesn't receive a cache update within 5 seconds, it also tries again. We do this to avoid hanging forever and failing all future tests.

In some cases (usually due to a bug in the test, but sometimes in the engine), we might hit this timeout but the condition still passes. When this happens, there's no clear indication that untilCacheCondition timed out. The only way to figure this out is to look at the timestamps in the log. This can result in tests exceeding their timeout threshold, but this is really hard to diagnose.

I've been bitten by this several times now. I think we should flag a test failure if the timeout is reached.

Otherwise, tests can take a very long time to run due to a bug without us realising that this is due to cache condition timeouts.

Assignee: nobody → jteh
Status: NEW → ASSIGNED
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/db31cf17952c
In a11y browser tests, treat a timeout in untilCacheCondition as a failure. r=eeejay
Flags: needinfo?(jteh)
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/73c83fecb157
In a11y browser tests, treat a timeout in untilCacheCondition as a failure. r=eeejay
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: