Closed Bug 1837000 Opened 1 year ago Closed 1 year ago

SpiderMonkey tasks and PGO builds crash when subsystem version is bumped to 10.0

Categories

(Firefox Build System :: Task Configuration, defect)

Product:
Firefox Build System
Component:
Task Configuration
Type:
defect

Tracking

(firefox117 fixed)

Status:
RESOLVED FIXED
Milestone:
117 Branch
Tracking Flags:
Tracking Status
firefox117 --- fixed

People

(Reporter: emk, Assigned: RyanVM)

References

(Blocks 2 open bugs)

Details

Attachments

(4 files)

live_backing.log
2.84 MB, application/octet-stream
Details
live_backing.log
77.31 KB, application/octet-stream
Details
Bug 1837000 - Switch jobs from b-win2012 workers to b-win2022.
48 bytes, text/x-phabricator-request
Details | Review
Bug 1837000 - Switch jobs from b-win2012 workers to b-win2022.
48 bytes, text/x-phabricator-request
jcristau
: approval-mozilla-esr115?
Details | Review

Because SpiderMonkey tasks are running on Windows 2012 (a.k.a. Windows 8/NT 6.x).

We should either upgrade the builder or lower the subsystem version (at least for SpiderMonkey).

Attached file live_backing.log —

:grandium pointed out that it will also affect PGO builds.

Summary: SpiderMonkey tasks crash when subsystem version is bumped to 10.0 → SpiderMonkey tasks and PGO builds crash when subsystem version is bumped to 10.0
Attached file live_backing.log —

I spy some win-2022 pools in ci-config, but they have alpha in the name so I'm not sure they're ready for use. Mark do you know if those could feasibly be used here? Or if not, is there bug we can set as blocking this?

Flags: needinfo?(mcornmesser)

(In reply to Andrew Halberstadt [:ahal] from comment #4)

I spy some win-2022 pools in ci-config, but they have alpha in the name so I'm not sure they're ready for use. Mark do you know if those could feasibly be used here? Or if not, is there bug we can set as blocking this?

Feel free to try that pool. It has been sometime since i have worked with it and can't remember the state it is in. We do have 2012 to 2022 migration in for H2 this year. Once I am back from PTO (6/26), I will look at getting us a functioning 2022 image to test gecko tasks against.

Ahal: could you create a bug requesting a 2022 image for use in CI and assign it to me?

Flags: needinfo?(mcornmesser)
No longer blocks: 1836875
Depends on: 1842921
Assignee: nobody → ryanvm
Status: NEW → ASSIGNED
Pushed by rvandermeulen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/148252770707 Switch jobs from b-win2012 workers to b-win2022. r=taskgraph-reviewers,releng-reviewers,jmaher,hneiva

Backed out as requested for making some corrections to the pool config.

Pushed by rvandermeulen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bd60ffa103f0 Switch jobs from b-win2012 workers to b-win2022. r=taskgraph-reviewers,releng-reviewers,jmaher,hneiva

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

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox117: --- → fixed
Resolution: --- → FIXED
Pushed by mkmelin@iki.fi: https://hg.mozilla.org/comm-central/rev/64cf58e75f5c Port to Thunderbird - Switch jobs from b-win2012 workers to b-win2022. rs=bustage-fix DONTBUILD
See Also: → 1843885
Component: Firefox-CI Administration → Task Configuration
Product: Release Engineering → Firefox Build System
Target Milestone: --- → 117 Branch
Attachment #9427713 - Flags: approval-mozilla-esr115?

esr115 Uplift Approval Request

  • User impact if declined: no user impact; relops would like to move away from the win2012 worker pools (bug 1920206)
  • Code covered by automated testing: yes
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: n/a
  • Risk associated with taking this patch: low
  • Explanation of risk level: we've been running these tasks on win2022 on trunk since 117
  • String changes made/needed: n/a
  • Is Android affected?: no
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: