lp:~vorlon/britney/+git/britney2-ubuntu

Author: Steve Langasek
Author Date: 2024-04-02 01:14:35 UTC

Handle ConnectionResetError from rabbitmq.

As seen in
https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/noble/2024-04-01/12:52:27.log

Having an entire britney run bail because of a connection reset is a bad
outcome!

Instead, catch this exception and avoid adding the test in question to the
list of queued tests (we can pick it up on the next run).

Possibly we should do more clever handling of a ConnectionResetError such as
reconnecting, but this is a minimum fix that will stop britney from aborting.

Author: Steve Langasek
Author Date: 2024-02-14 16:25:55 UTC

Add support in code for disabling ImplicitDependencyPolicy, and disable it

Author: Steve Langasek
Author Date: 2023-03-06 19:21:13 UTC

Add a dry-run option for the autopkgtest policy specifically

For rolling out britney on a new machine, we want to generate update_excuses
and update_output to confirm it's working correctly all the way through, so
we don't want to use the global --dry-run option; but we *do* want to
disable queuing tests and instead let the production instance of britney
queue the tests while we simply query the results. Add support for
ADT_ENABLE=dry-run in britney.conf, parallelling the behavior of other
policies.

Author: Steve Langasek
Author Date: 2022-08-23 22:05:50 UTC

More optimizations to not query unused baseline results

Author: Steve Langasek
Author Date: 2021-10-22 23:12:26 UTC

bdmurray-linting

Author: Steve Langasek
Author Date: 2021-10-07 08:08:45 UTC

--print-uninst and --nuninst-cache are not mutually-exclusive

This check has been present for a long time but there is no reason for it -
there is code elsewhere that explicitly checks for both options being set
together and DTRT. And this saves a minute on each britney run to not
regenerate uninstallability information that was just generated.

Author: Steve Langasek
Author Date: 2021-10-07 06:49:18 UTC

In the autopkgtest policy, cache the list of force-reset-test hints once

Due to the number of hints in standing use in Ubuntu, hints.search() is an
expensive operation, and we call it once for *every single test* referenced
from -proposed. Since force-reset-test are a small proportion of the hints
in use, searching once for all the hints of this type and only searching
this subset for each autopkgtest improves performance (with 23000
autopkgtests referenced in -proposed, this saves roughly 1 minute of
runtime, or 11% on a 9-minute britney run; the number of packages in
-proposed is typically much higher at other points in the release cycle,
therefore the absolute improvement in performance is expected to be
greater.)

The force-reset-test hints are an Ubuntu delta so this is not expected to be
upstreamed; and it could eventually be dropped if and when baseline
retesting is implemented in Ubuntu and the number of hints required drops.

This could be implemented with a more generic, elegant solution in
HintsCollection, but again, the scalability problem of hints is hopefully
short-lived so I didn't consider it worth the investment here.

Author: Steve Langasek
Author Date: 2021-10-06 19:54:11 UTC

Don't use expensive 'remove' hints

Since we've never used remove hints in Ubuntu and never will, we shouldn't
pay the cost for them in britney runs. Remove references to them entirely,
to speed up britney runs.

This is an Ubuntu delta not expected to be upstreamed, and can be dropped at
some future point when we don't have 11,000 active hints. (This count of
hints is expected to drop dramatically once we have autopkgtest baseline
retesting.)

Author: Steve Langasek
Author Date: 2020-01-21 05:37:51 UTC

test case for not running tests on dropped arch

Author: Steve Langasek
Author Date: 2018-09-20 13:34:18 UTC

Fix autopkgtests wrt the fact that excuses is no longer in the yaml

Author: Steve Langasek
Author Date: 2018-09-20 13:16:21 UTC

Don't use aptitude ever

Author: Steve Langasek
Author Date: 2018-03-03 01:01:31 UTC

As near as I can tell, the 'excuses' element within the yaml data is a
complete duplication of other structured data elsewhere in the yaml, and
does nothing but slow down the yaml parsing. So, just avoid emitting it.

Author: Steve Langasek
Author Date: 2017-07-07 04:14:19 UTC

Refine the logic for recording the nominal sent age of the mail

In the previous iteration, if we were ever down/frozen/disabled long enough
to miss sending two mails in a row, we would see unintended "catch-up"
behavior where each subsequent run of britney would send a mail until the
right total number of mails had been sent. Don't do this; instead, catch us
up in one go to the most recent mail that should have been sent, avoiding
bunching of notifications.

This changes one of the tests also to match.