Open Bug 1802850 Opened 3 years ago Updated 2 days ago

Intermittent TEST-UNEXPECTED-TIMEOUT | browser/components/resistfingerprinting/test/browser/browser_animationapi_iframes.js | single tracking bug

Categories

(Core :: Privacy: Anti-Tracking, defect, P5)

Product:
Core
Component:
Privacy: Anti-Tracking
Type:
defect

Tracking

()

Status:
REOPENED
Tracking Flags:
Tracking Status
firefox-esr102 --- unaffected
firefox107 --- unaffected
firefox108 --- unaffected
firefox109 --- wontfix
firefox110 --- wontfix

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: intermittent-failure, regression)

Attachments

(1 obsolete file)

Filed by: mlaza [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=397867228&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/WrdEhLpBSauoklN1wCq_Uw/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/WrdEhLpBSauoklN1wCq_Uw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

[task 2022-11-28T05:40:53.359Z] 05:40:53     INFO - TEST-PASS | browser/components/resistfingerprinting/test/browser/browser_animationapi_iframes.js | Test: test (A) - ''document.timeline.currentTime' should be rounded to nearest 0.02 ms; saw 1011.84 - 
[task 2022-11-28T05:40:53.359Z] 05:40:53     INFO - Buffered messages logged at 05:28:33
[task 2022-11-28T05:40:53.360Z] 05:40:53     INFO - Leaving test bound 
[task 2022-11-28T05:40:53.360Z] 05:40:53     INFO - Entering test bound 
[task 2022-11-28T05:40:53.361Z] 05:40:53     INFO - Buffered messages finished
[task 2022-11-28T05:40:53.361Z] 05:40:53    ERROR - TEST-UNEXPECTED-TIMEOUT | browser/components/resistfingerprinting/test/browser/browser_animationapi_iframes.js | application timed out after 740 seconds with no output
[task 2022-11-28T05:40:53.362Z] 05:40:53    ERROR - Force-terminating active process(es).
[task 2022-11-28T05:40:53.362Z] 05:40:53     INFO - Determining child pids from psutil...
[task 2022-11-28T05:40:53.362Z] 05:40:53     INFO - [2798, 2799, 2815, 2818, 3336, 3337, 3338, 3343]
[task 2022-11-28T05:40:53.363Z] 05:40:53     INFO - ==> process 2792 launched child process 2798
[task 2022-11-28T05:40:53.363Z] 05:40:53     INFO - ==> process 2792 launched child process 2799
[task 2022-11-28T05:40:53.363Z] 05:40:53     INFO - ==> process 2792 launched child process 2815
[task 2022-11-28T05:40:53.364Z] 05:40:53     INFO - ==> process 2792 launched child process 2816
...

:tjr, since you are the author of the regressor, bug 1778510, could you take a look?

For more information, please visit auto_nag documentation.

Flags: needinfo?(tom)

I am not sure what is causing this, I cannot reproduce it locally. I think I'm going to need to see how consistent this is.

Flags: needinfo?(tom)

This started to fail on tier 1: https://treeherder.mozilla.org/logviewer?job_id=398099665&repo=autoland&lineNumber=25822 with this failure message TEST-UNEXPECTED-TIMEOUT | browser/components/resistfingerprinting/test/browser/browser_animationapi_iframes.js | application timed out after 370 seconds with no output.

Summary: Intermittent TV [tier 2] TEST-UNEXPECTED-TIMEOUT | browser/components/resistfingerprinting/test/browser/browser_animationapi_iframes.js | single tracking bug → Intermittent TEST-UNEXPECTED-TIMEOUT | browser/components/resistfingerprinting/test/browser/browser_animationapi_iframes.js | single tracking bug

Hm. I suppose it's a problem with the framee not sending a message back to the framer and we're just stuck waiting.

But we're supposed to loop 30 times and if we haven't gotten anything by then, return an error. 30 x 100ms is only 3 seconds.

Set release status flags based on info from the regressing bug 1778510

status-firefox107: --- → unaffected
status-firefox108: --- → unaffected
status-firefox109: --- → affected
status-firefox-esr102: --- → unaffected

Set release status flags based on info from the regressing bug 1778510

status-firefox110: --- → affected

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit auto_nag documentation.

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox110: fix-optional → wontfix
Resolution: --- → INCOMPLETE

New failure instance: https://treeherder.mozilla.org/logviewer?job_id=409827439&repo=autoland

Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

Status: REOPENED → RESOLVED
Closed: 3 years ago → 2 years ago
Resolution: --- → INCOMPLETE

New failure instance: https://treeherder.mozilla.org/logviewer?job_id=434808692&repo=mozilla-central

Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Attachment #9383696 - Attachment is obsolete: true

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

Status: REOPENED → RESOLVED
Closed: 2 years ago → 1 year ago
Resolution: --- → INCOMPLETE

New failure instance: https://treeherder.mozilla.org/logviewer?job_id=493896766&repo=mozilla-esr128

Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: