gecko-dev/testing/web-platform/meta/workers/WorkerPerformanceNow.html.ini

prefs: [privacy.reduceTimerPrecision:false]
[WorkerPerformanceNow.html]
Bug 1435296 Address test failures caused by bumping timer precision to 2 ms r=baku There are a few different reasons why tests needed updating (not an exhaustive list): - Tests assume that successive operations take place at different times. - Tests assume that an operation took a minimum amount of time. - Tests hardcodes a specific delay. In most cases we hardcode the preference off. In some cases this is the best approach, in others, we would like to improve. The bug for tracking those improvements is Bug 1429648 An improvement that is present in some tests is to hardcode a specific precision reduction that is acceptable based on the confides of the test. (Obviously this needs to be a fix for the test framework and not a requirement on the feature being tested.) In a few places, the test itself can be fixed, for example to no longer require the end time of an operation to be strictly greater than the start time, and allows it to be equal to it. MozReview-Commit-ID: J59c7xQtZZJ --HG-- extra : rebase_source : df8a03e76eaf9cdc9524dbb3eb9035af237e534b 2018-02-12 20:39:41 +03:00			`prefs: [privacy.reduceTimerPrecision:false]`
Bug 1679466 - [wpt-sync] Update web-platform-tests to 35e691574b44ae6ff6251af68e619f5ddebfb07e, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 35e691574b44ae6ff6251af68e619f5ddebfb07e wpt-type: landing 2020-11-27 00:34:11 +03:00			`[WorkerPerformanceNow.html]`