Open Bug 1371906 Opened 7 years ago Updated 2 years ago

Intermittent browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | application timed out after 330/370 seconds with no output

Categories

(Core :: Security, defect, P2)

Product:
Core
Component:
Security
Type:
defect

Tracking

()

Status:
REOPENED

People

(Reporter: aryx, Assigned: tjr)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell unknown]) 

https://treeherder.mozilla.org/logviewer.html#?job_id=105978835&repo=autoland

23:02:37     INFO -  73 INFO TEST-PASS | browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | 'new File([], "").lastModifiedDate.getTime()' should be rounded to nearest 100 ms in workers; saw 1497049027100
23:02:37     INFO -  74 INFO TEST-PASS | browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | 'performance.now()' should be rounded to nearest 100 ms in workers; saw 500
23:02:37     INFO -  75 INFO TEST-PASS | browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | 'new Date().getTime()' should be rounded to nearest 100 ms in workers; saw 1497049027200
23:02:37     INFO -  76 INFO TEST-PASS | browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | 'new Event("").timeStamp' should be rounded to nearest 100 ms in workers; saw 500
23:02:37     INFO -  77 INFO TEST-PASS | browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | 'new File([], "").lastModified' should be rounded to nearest 100 ms in workers; saw 1497049027200
23:02:37     INFO -  78 INFO TEST-PASS | browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | 'new File([], "").lastModifiedDate.getTime()' should be rounded to nearest 100 ms in workers; saw 1497049027200
23:02:37     INFO -  Buffered messages finished
23:02:37  WARNING -  TEST-UNEXPECTED-TIMEOUT | browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | application timed out after 330 seconds with no output
Has this happened since June?  (would all occurrences be logged in this bug, or does the OrangeFactor 'bot skip some?)
Flags: needinfo?(aryx.bugmail)
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1371906&endday=2017-09-15&startday=2017-06-01&tree=trunk says we had 4 hits, all in June. Starred failures get always posted these days, at least on a weekly schedule. If I remember correct, low frequency failures didn't get posted until May or so.
Flags: needinfo?(aryx.bugmail)
If this comes back we can reopen and have someone from Ethan's team look at it.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Given the timing and frequency, this was actually a new failure, and last June was probably some bustage that was either backed out or fixed separately from this bug. The timing of this new case says it came from bug 1424341 / bug 1431425. There's going to be a fair number of them reported from the test-verify retriggers when bug 1431455 caused test-verify to look at this test, so TV will probably help with reproducing it.
Blocks: 1431425, 1424341
Flags: needinfo?(tom)
Assignee: nobody → tom
Flags: needinfo?(tom)
Priority: -- → P2
I had a weird feeling, or maybe saw an error message somewhere, that made me think this was being caused by this call in GetSpoofedUserAgent failing:

> nsCOMPtr<nsIXULAppInfo> appInfo =
>    do_GetService("@mozilla.org/xre/app-info;1", &rv);
Whiteboard: [stockwell unknown]
Summary: Intermittent browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | application timed out after 330 seconds with no output → Intermittent browser/components/resistfingerprinting/test/mochitest/test_reduce_time_precision.html | application timed out after 330/370 seconds with no output
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.