vs somehow doing it in autopkgtest cloud for each armhf request
Pro:
- this unblocks uploads happening now
- it actually adds all-proposed to the request so it shows up in the log
- as a result of the previous, retry-autopkgtest-regressions with --all-proposed works correctly
Cons:
- doesn't handle retries without all-proposed automagically
To solve the con or at least mostly (the checking for running tests in the client part is broken if you don't use --all-proposed), suggest Ubuntu QA to patch autopkgtest-cloud's webcontrol/request/submit.py to also insert all-proposed for noble armhf requests.
vs somehow doing it in autopkgtest cloud for each armhf request
Pro:
- this unblocks uploads happening now st-regressions with --all-proposed works correctly
- it actually adds all-proposed to the request so it shows up in the log
- as a result of the previous, retry-autopkgte
Cons:
- doesn't handle retries without all-proposed automagically
To solve the con or at least mostly (the checking for running tests in the client part is broken if you don't use --all-proposed), suggest Ubuntu QA to patch autopkgtest-cloud's webcontrol/ request/ submit. py to also insert all-proposed for noble armhf requests.