1497403 - Intermittent devtools/client/performance/test/browser_perf-recording-notices-03.js | Uncaught exception - at resource://devtools/shared/base-loader.js -> resource://devtools/client/performance/test/helpers/wait-utils.js:44 - Error: Predicate

Status: RESOLVED FIXED

(DevTools :: Performance Tools (Profiler/Timeline), defect, P5)

Description

[Treeherder Bug Filer]

Filed by: nerli [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=204125453&repo=mozilla-central

https://queue.taskcluster.net/v1/task/eISAUXdaRgqMgxo7tme_Rg/runs/0/artifacts/public/logs/live_backing.log

02:58:34     INFO - TEST-PASS | devtools/client/performance/test/browser_perf-recording-notices-03.js | Buffer percentage increased in display (1). - 
02:58:34     INFO - TEST-PASS | devtools/client/performance/test/browser_perf-recording-notices-03.js | Container has [buffer-status=in-progress] or [buffer-status=full]. - 
02:58:34     INFO - TEST-PASS | devtools/client/performance/test/browser_perf-recording-notices-03.js | Buffer status text has correct percentage. - 
02:58:34     INFO - Buffered messages logged at 02:55:44
02:58:34     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 2
02:58:34     INFO - Buffered messages logged at 02:55:46
02:58:34     INFO - Console message: [JavaScript Warning: "XrayWrapper denied access to property "wrappedJSObject" (reason: value shadows a property on the standard prototype). See https://developer.mozilla.org/en-US/docs/Xray_vision for more information. Note that only the first denied property access from a given global object will be reported." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/server/performance/profiler.js" line: 571}]
02:58:34     INFO - Buffered messages logged at 02:57:16
02:58:34     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 1
02:58:34     INFO - Buffered messages finished
02:58:34     INFO - TEST-UNEXPECTED-FAIL | devtools/client/performance/test/browser_perf-recording-notices-03.js | Uncaught exception - at resource://devtools/shared/base-loader.js -> resource://devtools/client/performance/test/helpers/wait-utils.js:44 - Error: Predicate returned false after 100 tries, aborting.
02:58:34     INFO - 
02:58:34     INFO - Stack trace:
02:58:34     INFO - exports.waitUntil@resource://devtools/shared/base-loader.js -> resource://devtools/client/performance/test/helpers/wait-utils.js:44:9
02:58:34     INFO - async*@chrome://mochitests/content/browser/devtools/client/performance/test/browser_perf-recording-notices-03.js:72:9
02:58:34     INFO - Async*Tester_execTest/<@chrome://mochikit/content/browser-test.js:1093:34
02:58:34     INFO - async*Tester_execTest@chrome://mochikit/content/browser-test.js:1084:16
02:58:34     INFO - nextTest/<@chrome://mochikit/content/browser-test.js:986:9
02:58:34     INFO - SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:795:59
02:58:34     INFO - Leaving test bound 
02:58:36     INFO - finish() was called, cleaning up...
02:58:55     INFO - GECKO(1488) | --DOMWINDOW == 4 (00000240A3BEE000) [pid = 4384] [serial = 99] [outer = 0000000000000000] [url = about:blank]
02:58:57     INFO - GECKO(1488) | MEMORY STAT | vsize 2259MB | vsizeMaxContiguous 132333732MB | residentFast 529MB | heapAllocated 171MB
02:58:57     INFO - TEST-OK | devtools/client/performance/test/browser_perf-recording-notices-03.js | took 284730ms
02:58:57     INFO - Not taking screenshot here: see the one that was previously logged
02:58:57     INFO - TEST-UNEXPECTED-FAIL | devtools/client/performance/test/browser_perf-recording-notices-03.js | Found an unexpected tab at the end of test run: http://example.com/browser/devtools/client/performance/test/doc_simple-test.html#1034444547330572 - 
02:58:57     INFO - GECKO(1488) | ++DOCSHELL 0000019C802E3000 == 1 [pid = 5304] [id = {0443a10c-7a6d-4559-a37b-26668439177d}]
02:58:57     INFO - GECKO(1488) | ++DOMWINDOW == 1 (0000019C80108400) [pid = 5304] [serial = 172] [outer = 0000000000000000]
02:58:57     INFO - GECKO(1488) | ++DOMWINDOW == 2 (0000019C801CD400) [pid = 5304] [serial = 173] [outer = 0000019C80108400]
02:58:57     INFO - checking window state

Comment 1

[Intermittent Failures Robot]

1 failures in 2740 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-central: 1

Platform breakdown:
* windows10-64-ccov: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1497403&startday=2018-10-08&endday=2018-10-14&tree=all

Comment 2

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup

Comment 3

[Cosmin Sabou [:CosminS]]

https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=267777231&repo=autoland&lineNumber=19382

Comment 4

[Intermittent Failures Robot]

1 failures in 4350 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 1

Platform breakdown:

• macosx1014-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1497403&startday=2019-09-16&endday=2019-09-22&tree=all

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 6

[Andreea Pavel [:apavel]]

Recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=276958766&repo=mozilla-inbound&lineNumber=14025

Comment 7

[Intermittent Failures Robot]

1 failures in 5444 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-inbound: 1

Platform breakdown:

• macosx1014-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1497403&startday=2019-11-18&endday=2019-11-24&tree=all

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 9

[Andreea Pavel [:apavel]]

Recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=287932645&repo=mozilla-central&lineNumber=5051

Comment 10

[Intermittent Failures Robot]

1 failures in 3364 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 1

Platform breakdown:

• linux1804-64-ccov: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1497403&startday=2020-02-03&endday=2020-02-09&tree=all

Comment 11

[Intermittent Failures Robot]

3 failures in 4690 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 3

Platform breakdown:

• linux1804-64-ccov: 3

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1497403&startday=2020-02-10&endday=2020-02-16&tree=all

Comment 12

[Alexandru Michis [:malexandru]]

This has quite a high failure rate on central:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&group_state=expanded&searchStr=linux%2C18.04%2Cx64%2Cccov%2Copt%2Cmochitests%2Ctest-linux1804-64-ccov%2Fopt-mochitest-devtools-chrome-e10s-3%2Cm%28dt3%29&tochange=5df075b6a6bb092533d786fefc350535dd940f67&fromchange=3b823d058ef541ec6abd5e781c6b9b4e1b893fbf&selectedJob=289302698

Julien,
Could you please redirect this to someone who can take a look?

Comment 13

[Intermittent Failures Robot]

15 failures in 4045 pushes (0.004 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 15

Platform breakdown:

• linux1804-64-ccov: 15

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1497403&startday=2020-02-17&endday=2020-02-23&tree=all

Comment 14

[Julien Wajsberg [:julienw]]

The fact that the error rate increased seem pretty new but I don't see what could have produced that.
This also only happens in ccov environment.

The stack trace isn't always the same.

Sometimes it fails at:

async*@chrome://mochitests/content/browser/devtools/client/performance/test/browser_perf-recording-notices-03.js:163:9

Sometimes at:

async*@chrome://mochitests/content/browser/devtools/client/performance/test/browser_perf-recording-notices-03.js:104:9

I'll try increasing some of the timeouts used in this file.

Comment 15

[Julien Wajsberg [:julienw]]

The approach of just increasing the timeouts didn't work, this seems to point to a flaw in the test itself.

FTR I don't plan to invest too much time in this, because this is testing some code we'll remove in a few months. If I can't fix it in a few hours I'll just disable the test in ccov.

Comment 16

[Julien Wajsberg [:julienw]]

Attachment: Bug 1497403 - Account for cases where the buffer gets full during the run of the test r=gregtatum

Comment 17

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ba7495a6fc87
Account for cases where the buffer gets full during the run of the test r=gregtatum

Comment 18

[Andrei Ciure[:aciure]]

https://hg.mozilla.org/mozilla-central/rev/ba7495a6fc87

Comment 19

[Intermittent Failures Robot]

3 failures in 5233 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 3

Platform breakdown:

• linux1804-64-ccov: 3

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1497403&startday=2020-02-24&endday=2020-03-01&tree=all