Closed Bug 1599197 Opened 8 months ago Closed 7 months ago

demote linux32 to tier-2, run builds not on autoland and try by default, only m-c

Categories

(Testing :: General, task, P3)

Version 3
task

Tracking

(firefox74 fixed)

RESOLVED FIXED
mozilla74
Tracking Status
firefox74 --- fixed

People

(Reporter: jmaher, Assigned: egao)

References

(Blocks 1 open bug)

Details

(Whiteboard: [ci-costs-2020:done])

Attachments

(3 files, 1 obsolete file)

currently we do linux32 builds on try, autoland, m-c and on m-c run wpt tests. We should stop running builds on autoland and by default on try.

See Also: → 1583673

we spend about $2700/month on linux32 builds on autoland and another $1100/month on Try.

Assuming 95% reduction on Autoland and 50% reduction on try we should see ~$3100/month or $37000/year in savings.

Assignee: nobody → egao
Priority: -- → P3

it appears we also have some unittests that run on autoland:

  • linux32-shippable :: WPT()
  • linux32-debug :: sm(arm)
  • linux32-buildrusttest

I assume when the builds stop, the process for pgo, build-signing, repackage-linux, and upload-generated-sources will automatically stop.

Tasks:

  • restrict linux32 builds to try and mozilla-central
  • restrict linux32 test jobs to try and mozilla-central
  • reduce linux32 test job to tier 2

:jmaher, I suspect the repackage tasks would need to have these lines removed?
https://searchfox.org/mozilla-central/source/taskcluster/ci/repackage/kind.yml#19-22

I think we can try landing a patch to remove linux32-shippable/opt builds from all repos other than mozilla-central and try, then see if we need to take the additional step of removing those lines.

Build-signing seems to be automatic if a shippable build is made, so presumably if the build no longer occurs on autoland then the signing should not occur.

Same as build-signing for upload-generated-sources.

Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1410db0871ba
demote linux32-shippable/opt tasks to tier 2 and limit builds to try and mozilla-central r=jmaher,gbrown
Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/dfa46920fe00
demote linux32-shippable/opt tasks to tier 2 and limit builds to try and mozilla-central r=jmaher,gbrown
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla74

we still do a lot of linux32 work:
https://treeherder.mozilla.org/#/jobs?repo=autoland&searchStr=build%2Clinux&fromchange=0d79d00528a411a5bd3e8d11944fc1609dccb283&tochange=12b3c389fd6dc093a05a7f3f8f11c7cc094f0a8a

we have linux32 debug and pgo builds continuing, I think the rust stuff is taken care of in another patch.

:egao, can you make another pass at disabling the linux32 debug and pgo builds on autoland?

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #11)

we still do a lot of linux32 work:
https://treeherder.mozilla.org/#/jobs?repo=autoland&searchStr=build%2Clinux&fromchange=0d79d00528a411a5bd3e8d11944fc1609dccb283&tochange=12b3c389fd6dc093a05a7f3f8f11c7cc094f0a8a

we have linux32 debug and pgo builds continuing, I think the rust stuff is taken care of in another patch.

:egao, can you make another pass at disabling the linux32 debug and pgo builds on autoland?

Yeah, I thought I'd need at least another pass or two to get everything down. Will do.

Flags: needinfo?(egao)

One source of truth in this bug:

linux32 builds need to continue running on the following:

  • mozilla-central
  • beta
  • release
  • esr

linux32 builds will not run by default on:

  • try
  • autoland
Attachment #9119171 - Attachment description: Bug 1599197 - only run linux32 builds on try/mozilla-central → Bug 1599197 - do not run linux32 on autoland or try by default

Question - how about the linux-gcp builds, should they also be restricted? Currently, linux-gcp/debug does not have any run-on-projects annotation.

Flags: needinfo?(jmaher)
Flags: needinfo?(gbrown)
Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/701fd0aec286
do not run linux32 on autoland or try by default r=jmaher,gbrown

gcp should be scheduled as tier-3 and on the same branches/frequencies as aws builds- I believe we are switching to gcp builds next week. So yes, lets move them to not run on autoland by default.

Flags: needinfo?(jmaher)

In addition, I still see the PGO process (4 jobs) running for linux shippable and generating builds. In some cases there is a signing job as well. Almost there.

Flags: needinfo?(gbrown)

Comment on attachment 9119827 [details]
Bug 1599197 - temporarily skip mfenced-12.html as it is interfering with the ubuntu1804 migration

Revision D59384 was moved to bug 1602863. Setting attachment 9119827 [details] to obsolete.

Attachment #9119827 - Attachment is obsolete: true

Strange. The changes I made to https://searchfox.org/mozilla-central/source/taskcluster/ci/instrumented-build/kind.yml#51 should have turned off PGO builds.

Attachment #9119947 - Attachment description: Bug 1599197 - turn off linux 32bit jobs on autoland, part 2 → Bug 1599197 - turn off linux 32bit jobs on autoland, part 3
Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c079dea037f7
turn off linux 32bit jobs on autoland, part 3 r=jmaher
Status: REOPENED → RESOLVED
Closed: 7 months ago7 months ago
Resolution: --- → FIXED
Regressions: 1616138
Whiteboard: [ci-costs-2020]
Whiteboard: [ci-costs-2020] → [ci-costs-2020:done]
Regressions: 1621295
You need to log in before you can comment on or make changes to this bug.