Upgrade xpcshell-test builders to use the testing node version rather than the build version
Categories
(Firefox Build System :: Toolchains, task)
Tracking
(firefox117 fixed)
| Tracking | Status | |
|---|---|---|
| firefox117 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
References
Details
Attachments
(1 file)
In bug 1762571 we had to limit the xpcshell-test builders to node 12 as we still supported Windows 7 and couldn't use the newer versions of node on there.
Bug 1836274 has now stopped the builders from running, so we can do the upgrade. This will put us back to the "builds run on the earlier version of node, but tests run on the latest" plan.
|
Assignee | |
Comment 1•11 months ago
|
||
|
|
Assignee | |
Comment 2•11 months ago
|
||
They were held back due to requiring support for Windows 7.
Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/314a103c82c8 Upgrade xpcshell-test builders to use the testing node version rather than an older one. r=firefox-build-system-reviewers,nalexander
|
||
Comment 4•11 months ago
|
||
| bugherder | ||
|
||
Comment 5•11 months ago
•
|
||
Mark, this has caused a spike in timeouts on Android xpcshell runs as seen here. From what I noticed they timeout when running this manifest netwerk/test/unit/xpcshell.ini , don't know if it's related or not.
Could you investigate what made them hit the timeout limit?
|
|
Assignee | |
Comment 6•11 months ago
|
||
(In reply to Cosmin Sabou [:CosminS] from comment #5)
Mark, this has caused a spike in timeouts on Android xpcshell runs as seen here. From what I noticed they timeout when running this manifest
netwerk/test/unit/xpcshell.ini, don't know if it's related or not.
Could you investigate what made them hit the timeout limit?
It looks like it is possible they did cause an issue. The logs all seem to be referencing adb: error: cannot bind listener: Address already in use though I'm not sure why.
Could you file a new bug under Testing -> xpcshell and we'll investigate from there?
Description
•