Closed Bug 1427918 Opened 3 years ago Closed 2 years ago
.html is almost permafail since the resolution of performance .now() was changed to 20us
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
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 email@example.com: https://hg.mozilla.org/mozilla-central/rev/7d81f423c7ff Disable Event-timestamp-high-resolution.html for frequent failures. r+a=bustage
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.
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
Is this issue relevant any longer since we're doing Fission?
Fixing Bug 1387894 should resolve it.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1387894
2 years ago
You need to log in before you can comment on or make changes to this bug.