Closed
Bug 1781237
Opened 2 years ago
Closed 2 years ago
Permafailling android pixel 2 chrome tests
Categories
(Testing :: Raptor, defect, P2)
Testing
Raptor
Tracking
(firefox105 affected)
RESOLVED
FIXED
105 Branch
Tracking | Status | |
---|---|---|
firefox105 | --- | affected |
People
(Reporter: sparky, Assigned: aglavic)
References
Details
Attachments
(1 file, 1 obsolete file)
All chrome tests on the pixel2 are currently permafailing, see here: https://treeherder.mozilla.org/jobs?repo=mozilla-central&tier=1%2C2%2C3&searchStr=chrome%2Cbrowsertime%2Cpixel&revision=00a40cdda673bdbe4f7831d1cf078909ad54182e
Relevant log portion:
[task 2022-07-25T21:36:00.017Z] 21:35:50 INFO - raptor-browsertime Info: Run tests on Pixel 2 [HT7A51A04660] using Android version 8.0.0
[task 2022-07-25T21:36:00.017Z] 21:35:50 INFO - raptor-browsertime Info: Running tests using Chrome - 1 iteration(s)
[task 2022-07-25T21:36:00.017Z] 21:35:51 INFO - raptor-browsertime Info: chrome failed to start, trying 2 more time(s): unknown error: com.android.chrome is not installed on device HT7A51A04660
[task 2022-07-25T21:36:00.017Z] 21:35:51 INFO - raptor-browsertime Info: chrome failed to start, trying 1 more time(s): unknown error: com.android.chrome is not installed on device HT7A51A04660
[task 2022-07-25T21:36:00.017Z] 21:35:51 INFO - raptor-browsertime Info: chrome failed to start, trying 0 more time(s): unknown error: com.android.chrome is not installed on device HT7A51A04660
[task 2022-07-25T21:36:00.017Z] 21:35:51 ERROR - raptor-browsertime Error: [chrome-m] Browsertime failed to run
[task 2022-07-25T21:36:00.017Z] 21:35:51 INFO - raptor-browsertime Info: at SeleniumRunner.start (/builds/task_165878474549360/fetches/browsertime/node_modules/browsertime/lib/core/seleniumRunner.js:87:13)
[task 2022-07-25T21:36:00.017Z] 21:35:51 INFO - raptor-browsertime Info: at processTicksAndRejections (node:internal/process/task_queues:96:5)
[task 2022-07-25T21:36:00.017Z] 21:35:51 INFO - raptor-browsertime Info: at async Iteration.run (/builds/task_165878474549360/fetches/browsertime/node_modules/browsertime/lib/core/engine/iteration.js:114:7)
[task 2022-07-25T21:36:00.017Z] 21:35:51 INFO - raptor-browsertime Info: at async Engine.runByScript (/builds/task_165878474549360/fetches/browsertime/node_modules/browsertime/lib/core/engine/index.js:266:20)
[task 2022-07-25T21:36:00.017Z] 21:35:51 INFO - raptor-browsertime Info: at async run (/builds/task_165878474549360/fetches/browsertime/node_modules/browsertime/bin/browsertime.js:74:22)
[task 2022-07-25T21:36:00.017Z] 21:35:51 ERROR - raptor-browsertime Error: [chrome-m] Browsertime failed to run
[task 2022-07-25T21:36:00.017Z] 21:35:51 CRITICAL - raptor-browsertime Critical: [chrome-m] No data to collect
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → aglavic
Assignee | ||
Comment 1•2 years ago
|
||
What we are doing:
- Disabling chrome-m tests to run on Pixel2 devices
Why:
- Recent bitbar cleanup script update is causing permafails on chrome
Assignee | ||
Comment 2•2 years ago
|
||
What we are doing:
- Disabling chrome-m tests to run on Pixel2 devices
Why:
- Recent bitbar cleanup script update is causing permafails on chrome
Updated•2 years ago
|
Attachment #9289267 -
Attachment is obsolete: true
Pushed by aglavic@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5bf851607e85 Skip chrome tests on Pixel2. r=perftest-reviewers,AlexandruIonescu
Comment 4•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox105:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
Reporter | ||
Comment 5•2 years ago
|
||
The issue hasn't been fixed so I've added the leave-open flag until then.
Updated•2 years ago
|
Assignee | ||
Comment 6•2 years ago
|
||
Waiting on finishing the transition from the P2 to a51s. Which assuming all goes well should be done by late December/early January
Comment 7•2 years ago
|
||
We're no longer running tests against Pixel 2, the A51 work will continue in bug 1780817.
Status: REOPENED → RESOLVED
Closed: 2 years ago → 2 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•