Closed
Bug 1942664
Opened 1 year ago
Closed 1 year ago
Increase time range for timing asserts in BiDi network event tests
Categories
(Remote Protocol :: WebDriver BiDi, task, P3)
Remote Protocol
WebDriver BiDi
Tracking
(firefox136 fixed)
RESOLVED
FIXED
136 Branch
| Tracking | Status | |
|---|---|---|
| firefox136 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webdriver:m15], [wptsync upstream])
Attachments
(1 file)
We haven't yet found a good way to have reliable timing assertions on Windows for BiDi network events. We keep having slightly off timings usually off by just 1 or 2 ms, but sometimes more (up to 20ms).
It's not clear where this might be coming from, so far all our attempts to modify preferences to reduce the issue have failed, so let's increase the time range we accept for the time being.
| Assignee | ||
Comment 1•1 year ago
|
||
Adds a helper to compute time range for BiDi network event timings assertions and
increases the allowed range by 100ms instead of 1ms to avoid intermittent issues on windows CI.
Updated•1 year ago
|
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4645596600ce
[wdspec] Increase time range for BiDi network events timing assertions r=webdriver-reviewers,Sasha
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/50207 for changes under testing/web-platform/tests
| Assignee | ||
Updated•1 year ago
|
Points: --- → 1
Priority: -- → P3
Whiteboard: [webdriver:m15]
| Assignee | ||
Updated•1 year ago
|
Points: 1 → 2
Comment 4•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox136:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
Upstream PR merged by moz-wptsync-bot
Whiteboard: [webdriver:m15] → [webdriver:m15], [wptsync upstream]
You need to log in
before you can comment on or make changes to this bug.
Description
•