Merge lp:~vorlon/britney/turn-on-arm64-slowly into lp:~ubuntu-release/britney/britney1-ubuntu
Proposed by
Steve Langasek
Status: | Rejected |
---|---|
Rejected by: | Steve Langasek |
Proposed branch: | lp:~vorlon/britney/turn-on-arm64-slowly |
Merge into: | lp:~ubuntu-release/britney/britney1-ubuntu |
Diff against target: |
23 lines (+9/-4) 1 file modified
britney (+9/-4) |
To merge this branch: | bzr merge lp:~vorlon/britney/turn-on-arm64-slowly |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ubuntu Release Team | Pending | ||
Iain Lane | Pending | ||
Review via email: mp+333696@code.launchpad.net |
Description of the change
We don't have arm64 autopkgtest capacity to handle running the autopkgtests consistently for devel, but we have worked through setting a baseline for the stable releases (xenial and forward) and our single test runner might be able to keep up with the autopkgtest demand just from SRUs. Turn this on initially for xenial only in order to see.
To post a comment you must log in.
Unmerged revisions
- 311. By Steve Langasek
-
Rolling enablement of autopkgtests for arm64 in britney: turn it on first only for xenial and see how it goes with the SRUs
Hi Steve,
On Tue, Nov 14, 2017 at 04:37:55PM -0000, Steve Langasek wrote:
> We don't have arm64 autopkgtest capacity to handle running the
> autopkgtests consistently for devel, but we have worked through
> setting a baseline for the stable releases (xenial and forward) and
> our single test runner might be able to keep up with the autopkgtest
> demand just from SRUs.
Hmm, seeing you write this makes me think that you're not aware that
bos02 is up and running. I suppose I forgot to communicate this widely
enough - I thought you were aware because I've been watching the queues
for the other releases fill up in sequence as the previous one finishes.
I think we *do* have capacity to turn on proposed-migration for arm64
for every release if we want to. Currently we have 40 workers handling
arm64 and s390x.
> Turn this on initially for xenial only in order to see.
Go for it. I thought you were establishing a baseline by doing an
initial run. If you are doing this, please feel free to turn on releases
once the baseline run is finished. If you don't think that is important,
please also feel free to turn on all releases right away if you think
that's best - with no baseline run it shouldn't be much of a burden for
bionic even.
Cheers,
--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]