Closed
Bug 1427918
Opened 6 years ago
Closed 5 years ago
Event-timestamp-high-resolution.html is almost permafail since the resolution of performance.now() was changed to 20us
Categories
(Core :: DOM: Events, enhancement, P3)
Core
DOM: Events
Tracking
()
RESOLVED
DUPLICATE
of bug 1387894
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox57 | --- | disabled |
firefox58 | --- | disabled |
firefox59 | --- | disabled |
People
(Reporter: RyanVM, Unassigned)
References
Details
In bug 1427870, we had to change the resolution of performance.now() from 5us to 20us. This is causing Event-timestamp-high-resolution.html permafails now as a result. I'm going to annotate my way to victory for the time-being since this is time-sensitive, but given that this change is being shipped across all vendors, the test will probably need some sort of longer-term fix as well. https://treeherder.mozilla.org/logviewer.html#?job_id=153979112&repo=mozilla-release
Reporter | ||
Comment 1•6 years ago
|
||
Not that this test was very reliable to begin with. See bug 1387894.
See Also: → 1387894
Reporter | ||
Comment 2•6 years ago
|
||
I pushed the annotation update to m-c and will soon do the same for Beta & Release: https://hg.mozilla.org/mozilla-central/rev/25d2937fa7dd7f7a697c4ba053959f4cf4416af6 However, I fully expect to also file a new intermittent-failure bug for unexpected passes since this isn't 100% permafailing. But I think it'll still be more manageable than the current failures.
Summary: Event-timestamp-high-resolution.html permafails with the resolution of performance.now() changed to 20us → Event-timestamp-high-resolution.html is almost permafail since the resolution of performance.now() was changed to 20us
Pushed by ryanvm@gmail.com: https://hg.mozilla.org/mozilla-central/rev/7d81f423c7ff Disable Event-timestamp-high-resolution.html for frequent failures. r+a=bustage
Reporter | ||
Comment 4•6 years ago
|
||
The change in comment 2 didn't work because wpt treats global annotations as separate from subtest annotations :(. Since the failures happen unpredictably in various subtests, I don't see any other option besides disabling the test on opt builds for now, which is what the commit in comment 3 does.
Reporter | ||
Comment 5•6 years ago
|
||
uplift |
Disabled on Beta & Release: https://hg.mozilla.org/releases/mozilla-beta/rev/e9d14df9e8a06acb176ff9f502da8866f479cc90 https://hg.mozilla.org/releases/mozilla-release/rev/4d3497f26bc179ce5632719a808e32335e8cec4d
Comment 6•6 years ago
|
||
baku, can you take a look here? Maybe Andreas can help you. bkelly brought up the good question of whether or not we should raise a spec issue about changing the resolution to be 20 μs.
Flags: needinfo?(amarchesini)
Flags: needinfo?(afarre)
Comment 7•6 years ago
|
||
(In reply to Andrew Overholt [:overholt] from comment #6) > bkelly brought up the good question of whether or not we should raise a spec > issue about changing the resolution to be 20 μs. 20ms is a stopgap. I think any spec changes would be considerably more expansive of that, and would aim to frustrate or prevent high resolution timers from being constructed from any browser feature. *Alternately* we could consider the notion that providing high resolution timing information (either in javascript or to user-mode code via rtdsc) is a perfectly acceptable thing to do. It sounds quite reasonable right? The implication of such a declaration is that *any* software or hardware mechanism that allows privilege boundary bypasses is a bug, from microcode in SPECTRE to non-constant time animation rendering to non-cache neutral crypto algorithms to...
Comment 8•6 years ago
|
||
FYI, Spectre and Meltdown should be discussed tomorrow during webperf wg conf call https://lists.w3.org/Archives/Public/public-web-perf/2018Jan/0001.html
Comment hidden (offtopic) |
Updated•6 years ago
|
Priority: -- → P3
Comment 10•5 years ago
|
||
Is this issue relevant any longer since we're doing Fission?
Flags: needinfo?(afarre)
Comment 11•5 years ago
|
||
Fixing Bug 1387894 should resolve it.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Updated•5 years ago
|
Flags: needinfo?(amarchesini)
Updated•5 years ago
|
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•