No way to mark a test as 'accepted regression'
Bug #1688516 reported by
Iain Lane
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
Fix Released
|
Undecided
|
Julian Andres Klode |
Bug Description
Let's say we know a package has regressed on an arch, and it's not going to get better and the release team has accepted this. They'd force-badtest the package so it migrates despite the failing test.
This hint would either have a version and have to be bumped every time, or it would have 'all' as a version.
In the 'all' case, if the test *does* get fixed, we would ignore any subsequent regressions whereas we'd probably want to at least consider it.
Proposal: a new hint type that forgets pass results before the specified version: force-alwaysfail foo/version[/arch].
Related branches
~juliank/britney/+git/britney2-ubuntu:lp1688516
Merged
into
~ubuntu-release/britney/+git/britney2-ubuntu:master
at
revision 04c3cdb382c2a94382187fd76139d88dec3c5f8d
- Iain Lane: Needs Fixing
-
Diff: 229 lines (+162/-6)3 files modifiedbritney2/policies/autopkgtest.py (+31/-4)
britney2/utils.py (+0/-2)
tests/test_autopkgtest.py (+131/-0)
Changed in auto-package-testing: | |
status: | New → In Progress |
assignee: | nobody → Julian Andres Klode (juliank) |
To post a comment you must log in.
Cross-linking to bug #1700668; not marking either as a duplicate until we decide which approach we want to take.
I argue in that bug that requiring setting of that hint is manual busywork for the release team, and that we should instead change our definition of a "regressed" autopkgtest.