Closed Bug 1461298 Opened 6 years ago Closed 6 years ago

Intermittent /user-timing/measure_associated_with_navigation_timing.html | Second measure of current mark to navigationStart should be negative value. - assert_true: Second measure of current mark to navigationStart should be negative value.

Categories

(Core :: DOM: Core & HTML, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure)

08:22:03 INFO - TEST-START | /user-timing/measure_associated_with_navigation_timing.html 08:22:03 INFO - 08:22:03 INFO - TEST-PASS | /user-timing/measure_associated_with_navigation_timing.html | Measure of navigationStart to now should be positive value. 08:22:03 INFO - TEST-PASS | /user-timing/measure_associated_with_navigation_timing.html | Measure of navigationStart to loadEventEnd should be positive value. 08:22:03 INFO - TEST-PASS | /user-timing/measure_associated_with_navigation_timing.html | Measure of current mark to navigationStart should be negative value. 08:22:03 INFO - TEST-PASS | /user-timing/measure_associated_with_navigation_timing.html | loadTime plus loadEventEnd to a mark "a" should equal to navigationStart to "a". 08:22:03 INFO - TEST-UNEXPECTED-FAIL | /user-timing/measure_associated_with_navigation_timing.html | Second measure of current mark to navigationStart should be negative value. - assert_true: Second measure of current mark to navigationStart should be negative value. expected true got false 08:22:03 INFO - test_greater_than/<@http://web-platform.test:8000/user-timing/resources/webperftestharness.js:123:27 08:22:03 INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1490:20 08:22:03 INFO - test@http://web-platform.test:8000/resources/testharness.js:500:9 08:22:03 INFO - wp_test@http://web-platform.test:8000/common/performance-timeline-utils.js:17:3 08:22:03 INFO - test_greater_than@http://web-platform.test:8000/user-timing/resources/webperftestharness.js:123:5 08:22:03 INFO - onload_test@http://web-platform.test:8000/user-timing/measure_associated_with_navigation_timing.html:39:5 08:22:03 INFO - setTimeout handler*onload@http://web-platform.test:8000/user-timing/measure_associated_with_navigation_timing.html:1:1 08:22:03 INFO - 08:22:03 INFO - TEST-PASS | /user-timing/measure_associated_with_navigation_timing.html | Measures of loadTime should have same duration. 08:22:03 INFO - TEST-UNEXPECTED-FAIL | /user-timing/measure_associated_with_navigation_timing.html | Measure from domComplete event to most recent mark "a" should have longer duration. - assert_true: Measure from domComplete event to most recent mark "a" should have longer duration. expected true got false 08:22:03 INFO - test_greater_than/<@http://web-platform.test:8000/user-timing/resources/webperftestharness.js:123:27 08:22:03 INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1490:20 08:22:03 INFO - test@http://web-platform.test:8000/resources/testharness.js:500:9 08:22:03 INFO - wp_test@http://web-platform.test:8000/common/performance-timeline-utils.js:17:3 08:22:03 INFO - test_greater_than@http://web-platform.test:8000/user-timing/resources/webperftestharness.js:123:5 08:22:03 INFO - onload_test@http://web-platform.test:8000/user-timing/measure_associated_with_navigation_timing.html:41:5 08:22:03 INFO - setTimeout handler*onload@http://web-platform.test:8000/user-timing/measure_associated_with_navigation_timing.html:1:1 08:22:03 INFO - 08:22:03 INFO - TEST-UNEXPECTED-FAIL | /user-timing/measure_associated_with_navigation_timing.html | Measure from most recent mark to navigationStart should have longer duration. - assert_true: Measure from most recent mark to navigationStart should have longer duration. expected true got false 08:22:03 INFO - test_greater_than/<@http://web-platform.test:8000/user-timing/resources/webperftestharness.js:123:27 08:22:03 INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1490:20 08:22:03 INFO - test@http://web-platform.test:8000/resources/testharness.js:500:9 08:22:03 INFO - wp_test@http://web-platform.test:8000/common/performance-timeline-utils.js:17:3 08:22:03 INFO - test_greater_than@http://web-platform.test:8000/user-timing/resources/webperftestharness.js:123:5 08:22:03 INFO - onload_test@http://web-platform.test:8000/user-timing/measure_associated_with_navigation_timing.html:42:5 08:22:03 INFO - setTimeout handler*onload@http://web-platform.test:8000/user-timing/measure_associated_with_navigation_timing.html:1:1
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → INCOMPLETE
If it helps whoever looks into this, I'm hitting this pretty frequently on my try pushes for getting wpt running on Firefox for Android: https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&group_state=expanded&author=wkocher%40mozilla.com&searchStr=43a204dad26579b20f71d20bc05a0f92bfed8466&fromchange=f841ec1727c3b974207ca5f009da49bacc518297&selectedJob=207423090 I haven't been able to reproduce it locally in an android emulator, but more times than not it fails with this error. These Android try jobs aren't runnable by default yet, so if you want to get them to run on try, you'll need to include this patch in your try push: https://hg.mozilla.org/try/rev/de29e2276e658a4c7817a42c7ff2dbf8d8743933
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → INCOMPLETE
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.