Merge ~paelzer/britney/+git/hints-ubuntu:mitigate-flaky-apt-clone into ~ubuntu-release/britney/+git/hints-ubuntu:devel

Proposed by Christian Ehrhardt 
Status: Merged
Merged at revision: 9079d9afe194b3c838828769af57806234b524c5
Proposed branch: ~paelzer/britney/+git/hints-ubuntu:mitigate-flaky-apt-clone
Merge into: ~ubuntu-release/britney/+git/hints-ubuntu:devel
Diff against target: 14 lines (+2/-1)
1 file modified
ubuntu-release (+2/-1)
Reviewer Review Type Date Requested Status
Iain Lane Approve
Review via email: mp+393306@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

For details please see the old discussion that led to the badtest in the past in bug 1510060 and my recheck that shows it to be still the same issue in bug 1902830.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

FYI there actually is a fix that we can upload instead or in addition to this badtest.
See: https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/1902830/comments/3

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

FYI sshuttle tests are resolved by some combined test triggers (also held python-apt back).

apt-clone will eventually be resolved by https://code.launchpad.net/~paelzer/apt-clone/apt-clone-fix-fails-early-cycle/+merge/393310 as it seems to become approved.

Due to that I'm changing this change here to be a reset-test on the current version.
We know the current one is bad and need to unblock things asap.
At the same time we now know/expect that the next version will be good - so a reset will do.

Together that would to asap unblock the effect of bug 1902830 on a bunch of automated testing that stalls early 21.04 and after a new upload of apt-clone we have hopefully more reliable good results.

Revision history for this message
Iain Lane (laney) wrote :

Thanks.

Please could you take care of syncing apt-clone when it becomes available to sync? If it’s flaky then force-reset-test doesn’t help much of course.

Regarding sshuttle, the ‘extra’ triggers you added will need to be made to migrate too, otherwise future runs will probably keep on failing.

review: Approve
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

I wanted to sync this morning but MVO was faster and actually we'll need 0.4.3 but all that is going on. Thanks!

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/ubuntu-release b/ubuntu-release
2index 6ee77b4..df0c778 100644
3--- a/ubuntu-release
4+++ b/ubuntu-release
5@@ -10,7 +10,8 @@ force-reset-test abi-monitor/1.12-2/armhf abi-monitor/1.12-2/i386
6 force-reset-test abi-monitor/1.12.2ubuntu1/amd64 abi-monitor/1.12.2ubuntu1/ppc64el
7 force-reset-test adequate/0.15.1ubuntu5
8 force-reset-test apparmor/2.13.3-7ubuntu6
9-force-reset-test apt-clone/0.4.1ubuntu2
10+# Keeps on regressing - see LP: #1510060 hopefully better after LP: #1902830
11+force-reset-test apt-clone/0.4.1ubuntu5
12 ## python removal
13 force-reset-test apport/2.20.11-0ubuntu16
14 ##

Subscribers

People subscribed via source and target branches