[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1028612: marked as done (unblock: pam/1.5.2-6)

Your message dated Fri, 13 Jan 2023 21:54:15 +0100
with message-id <209e6f5d-bb66-2fff-2562-cae1c7d95529@debian.org>
and subject line Re: Bug#1028612: unblock: pam/1.5.2-6
has caused the Debian Bug report #1028612,
regarding unblock: pam/1.5.2-6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1028612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028612
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pam@packages.debian.org
Control: affects -1 + src:pam

Please unblock package pam
If I am reading https://qa.debian.org/excuses.php?package=pam
right, it looks like pam is blocked by a supposed regression on squid on s390x.
I assume the mmdebstrap regression should not block because the version in unstable has the regression but the version in testing does not.

As far as I can tell both the squid regression and the mmdebstrap regression are flaky tests.
The squid regression particularly: on one arch, the ftp test fails.

I used the ci.debian.net self service to request a rerun of squid from testing with pam from unstable on s390x
and my run
https://ci.debian.net/data/autopkgtest/testing/s390x/s/squid/30263099/log.gz

appears to have succeed.
So I think the test is flaky.

Unless I've missed something else, I think that the test failures should be ignored and pam accepted into testing.

--- End Message ---
--- Begin Message --- 
Hi Sam,

On 13-01-2023 16:54, Sam Hartman wrote:

Please unblock package pam
If I am reading https://qa.debian.org/excuses.php?package=pam
right, it looks like pam is blocked by a supposed regression on squid on s390x.
I assume the mmdebstrap regression should not block because the version in unstable has the regression but the version in testing does not.
Both retries succeeded, so my expectation is that pam will just migrate without us doing anything.
For your info, failures are rescheduled automatically after 1 day the failing result came in. flaky tests should normally don't show up so long, but s390x is slow at this moment and ppc64el isn't particularly fast either, so there wasn't a retry yet. Next time instead of triggering under your own credentials, consider hitting the retry button (recycle symbol, not sure how "visible" that is for you) and ignore potential "already scheduled" signs. A job scheduled by a human with default priority is higher in priority that the automated jobs from britney, even if you retry a job that originated from britney. 

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: