Merge ~enr0n/britney:force-badtest-snapd into ~ubuntu-release/britney/+git/hints-ubuntu:impish

Proposed by Nick Rosbrook
Status: Rejected
Rejected by: Steve Langasek
Proposed branch: ~enr0n/britney:force-badtest-snapd
Merge into: ~ubuntu-release/britney/+git/hints-ubuntu:impish
Diff against target: 11 lines (+3/-0)
1 file modified
ubuntu-sru (+3/-0)
Reviewer Review Type Date Requested Status
Steve Langasek Needs Information
Review via email: mp+418553@code.launchpad.net
To post a comment you must log in.
Revision history for this message
William Wilson (jawn-smith) wrote :

LGTM

Revision history for this message
Steve Langasek (vorlon) wrote :

The normal preferred approach now is to do a migration-reference/0 retest (--no-proposed, in retry-autopkgtest-regressions) to demonstrate that the regression in question is reproducible in the release (or -updates) pocket. Is there a reason not to do this here?

review: Needs Information
Revision history for this message
Steve Langasek (vorlon) wrote :

Using tools from lp:ubuntu-archive-tools:

$ retry-autopkgtest-regressions --series impish --blocks systemd --no-proposed | xargs -rn1 -P10 wget --load-cookies ~/.cache/autopkgtest.cookie -O-

I've run this now and will wait for results.

Revision history for this message
William Wilson (jawn-smith) wrote :

@vorlon: The reason I didn't have enr0n do that is because we know that this test is broken and we know exactly why. We'll need to SRU snapd, but are trying to get systemd to migrate in the meantime.

Revision history for this message
Steve Langasek (vorlon) wrote :

Ok, I'm not sure why that means you want a static hint in a file which must be edited by a member of the SRU team, vs accurate and self-updating information in the autopkgtest database that any Ubuntu developer can fix.

Historically, my threshold for adding badtest hints is "show me that the baseline has regressed, or explain to me why we should add a hint that accepts a new regression". With baseline retesting, proving that the baseline has regressed immediately means you don't have to talk to me about it.

Revision history for this message
William Wilson (jawn-smith) wrote :

It seems I misunderstood the functionality of the migration-reference/0 test. I thought it would just demonstrate that the tests for the package had regressed, and that a hint was still needed to not block on the regression. Looking at the excuses page though it looks like I was incorrect about that.

Revision history for this message
Steve Langasek (vorlon) wrote :

Cool, closing this mp then!

Unmerged commits

bd700f7... by Nick Rosbrook

ubuntu-sru: force-badtest snapd/2.54.3+21.10.1ubuntu0.2

A snapd issue is blocking many tests in impish.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/ubuntu-sru b/ubuntu-sru
2index adea1fb..123ca4b 100644
3--- a/ubuntu-sru
4+++ b/ubuntu-sru
5@@ -3,3 +3,6 @@ force-reset-test adsys/0.7.1/arm64
6
7 # This test hasn't passed in a couple of years
8 force-badtest assimp/5.0.1~ds0-2/armhf
9+
10+# snapd regression is blocking many packages in impish
11+force-badtest snapd/2.54.3+21.10.1ubuntu0.2

Subscribers

People subscribed via source and target branches