1196019 - Intermittent browser_markers-gc.js | Test timed out | Found a tab after previous test timed out

Status: RESOLVED WORKSFORME

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

Description

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

12 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_markers-gc.js | Test timed out - expected PASS
15 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_markers-gc.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_force_gc.html - expected PASS
34 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_markers-parse-html.js | A promise chain failed to handle a rejection: - at chrome://mochitests/content/browser/browser/devtools/performance/test/head.js:141 - ReferenceError: ok is not defined

Comment 1

[Legacy TBPL/Treeherder Robot]

log: https://treeherder.mozilla.org/logviewer.html#?repo=fx-team&job_id=4289174
repository: fx-team
start_time: 2015-08-18T12:39:54
who: wkocher[at]mozilla[dot]com
machine: tst-linux32-spot-278
buildname: Ubuntu VM 12.04 fx-team debug test mochitest-devtools-chrome-5
revision: 13bb29917965

12 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_markers-gc.js | Test timed out - expected PASS
15 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_markers-gc.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_force_gc.html - expected PASS
34 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_markers-parse-html.js | A promise chain failed to handle a rejection:  - at chrome://mochitests/content/browser/browser/devtools/performance/test/head.js:141 - ReferenceError: ok is not defined
84 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-categories-js-calltree.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
148 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-clear-01.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
227 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-clear-02.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
277 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-columns-js-calltree.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
326 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-columns-memory-calltree.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
350 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-01.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
382 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-04.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
418 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-05.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
448 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-06.js | Test timed out - expected PASS
451 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-06.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_simple-test.html - expected PASS
490 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-07.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
512 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-08.js | Test timed out - expected PASS
515 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-08.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_simple-test.html - expected PASS
518 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-09.js | A promise chain failed to handle a rejection:  - at resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/protocol.js:1125 - Error: Connection closed, pending request to server1.conn18.performanceActor21, type startRecording failed
535 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-console-record-09.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
542 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-01.js | Test timed out - expected PASS
545 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-01.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_simple-test.html - expected PASS
586 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-02.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - expected PASS
611 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-03.js | Test timed out - expected PASS
614 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-03.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_simple-test.html - expected PASS
617 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-04.js | A promise chain failed to handle a rejection:  - at resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/protocol.js:1125 - Error: Connection closed, pending request to server1.conn22.performanceActor21, type stopRecording failed
651 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-04.js | Test timed out - expected PASS
654 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-04.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_simple-test.html - expected PASS
ReferenceError: info is not defined: onEvent@chrome://mochitests/content/browser/browser/devtools/performance/test/head.js:157:9
ReferenceError: info is not defined: onEvent@chrome://mochitests/content/browser/browser/devtools/performance/test/head.js:157:9
669 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-05.js | Test timed out - expected PASS
672 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-05.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_simple-test.html - expected PASS
675 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-06.js | A promise chain failed to handle a rejection:  - at resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/protocol.js:1125 - Error: Connection closed, pending request to server1.conn24.performanceActor21, type startRecording failed
701 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-06.js | Test timed out - expected PASS
704 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-06.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_simple-test.html - expected PASS
ReferenceError: info is not defined: onEvent@chrome://mochitests/content/browser/browser/devtools/performance/test/head.js:157:9
720 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-07.js | Test timed out - expected PASS
723 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-07.js | Found a tab after previous test timed out: http://example.com/browser/browser/devtools/performance/test/doc_simple-test.html - expected PASS
ReferenceError: info is not defined: onEvent@chrome://mochitests/content/browser/browser/devtools/performance/test/head.js:157:9
729 INFO TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-calltree-render.js | A promise chain failed to handle a rejection:  - at chrome://browser/content/devtools/performance/views/overview.js:200 -
TEST-UNEXPECTED-TIMEOUT | browser/devtools/performance/test/browser_perf-details-calltree-render.js | application timed out after 330 seconds with no output
TEST-UNEXPECTED-FAIL | ShutdownLeaks | process() called before end of test suite
TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-details-calltree-render.js | application terminated with exit code 6
PROCESS-CRASH | browser/devtools/performance/test/browser_perf-details-calltree-render.js | application crashed [@ linux-gate.so + 0x424]
TEST-UNEXPECTED-FAIL | leakcheck | default process: missing output line for total leaks!
command timed out: 4800 seconds elapsed running ['/tools/buildbot/bin/python', 'scripts/scripts/desktop_unittest.py', '--cfg', 'unittests/linux_unittest.py', '--mochitest-suite', 'mochitest-devtools-chrome-chunked', '--total-chunks', '8', '--this-chunk', '5', '--blob-upload-branch', 'fx-team', '--download-symbols', 'true'], attempting to kill

Comment 2

[David Burns :automatedtester]

[Mass Closure] Closing Intermittent as a one off