demote linux32 to tier-2, run builds not on autoland and try by default, only m-c
Categories
(Testing :: General, task, P3)
Tracking
(firefox74 fixed)
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.
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
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.
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Reporter | ||
Comment 2•5 years ago
|
||
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.
Assignee | ||
Comment 3•5 years ago
|
||
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
Assignee | ||
Comment 4•5 years ago
|
||
: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
.
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Google group post: https://groups.google.com/forum/#!topic/mozilla.dev.platform/dsVeni30-38
Comment 8•5 years ago
|
||
Backed out changeset 1410db0871ba (bug 1599197) for causing linting failures
push that caused the backout: https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedJob=283651362&resultStatus=testfailed%2Cbusted%2Cexception%2Cusercancel%2Crunnable&revision=1410db0871ba5a00a43906437e0050b19bc363bc
backout: https://hg.mozilla.org/integration/autoland/rev/5e47df675103bcf1914b61c2060b7c06ab31e290
Comment 10•5 years ago
|
||
bugherder |
Reporter | ||
Comment 11•5 years ago
|
||
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?
Updated•5 years ago
|
Assignee | ||
Comment 12•5 years ago
|
||
(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=12b3c389fd6dc093a05a7f3f8f11c7cc094f0a8awe 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.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 13•5 years ago
|
||
Assignee | ||
Comment 14•5 years ago
|
||
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
Updated•5 years ago
|
Assignee | ||
Comment 15•5 years ago
|
||
Question - how about the linux-gcp
builds, should they also be restricted? Currently, linux-gcp/debug
does not have any run-on-projects
annotation.
Comment 16•5 years ago
|
||
Comment 17•5 years ago
|
||
bugherder |
Reporter | ||
Comment 18•5 years ago
|
||
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.
Reporter | ||
Comment 19•5 years ago
|
||
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.
Updated•5 years ago
|
Assignee | ||
Comment 20•5 years ago
|
||
Comment 21•5 years ago
|
||
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.
Assignee | ||
Comment 22•5 years ago
|
||
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.
Assignee | ||
Comment 23•5 years ago
|
||
Updated•5 years ago
|
Comment 24•5 years ago
|
||
Assignee | ||
Comment 25•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Comment 26•5 years ago
|
||
bugherder |
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Description
•