Intermittent Launcher specs Puppeteer Puppeteer.launch should work with no default arguments (launcher.spec.ts) | expected PASS
Categories
(Remote Protocol :: CDP, defect, P5)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: intermittent-failure)
Filed by: hskupin [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=354624686&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/d0eTGfHqTLeYvfcPCaezzg/runs/0/artifacts/public/logs/live_backing.log
https://treeherder.mozilla.org/logviewer?job_id=354624686&repo=try&lineNumber=24814-24818
[task 2021-10-13T09:56:37.411Z] TEST-START | Launcher specs Puppeteer Puppeteer.launch should work with no default arguments (launcher.spec.ts)
[task 2021-10-13T09:56:37.411Z] PID 408 | ["test-start",{"title":"should work with no default arguments","fullTitle":"Launcher specs Puppeteer Puppeteer.launch should work with no default arguments","file":"/builds/worker/checkouts/gecko/remote/test/puppeteer/test/launcher.spec.ts","currentRetry":0}]
[task 2021-10-13T09:56:37.445Z] PID 408 | Unable to init server: Could not connect: Connection refused
[task 2021-10-13T09:56:37.445Z] PID 408 | Error: cannot open display: :0
[task 2021-10-13T09:56:37.450Z] TEST-UNEXPECTED-FAIL | Launcher specs Puppeteer Puppeteer.launch should work with no default arguments (launcher.spec.ts) | expected PASS
Comment 1•4 years ago
|
||
This is actually caused by not having a window server environment setup for running this specific test. It's somehow not running as headless, and as such Firefox fails during startup. The work on bug 1669435 might help here.
| Comment hidden (Intermittent Failures Robot) |
Comment 3•4 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit auto_nag documentation.
Description
•