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

Bug#1104335: marked as done (britney/debci: sometimes lists a non-regression fail as a regression)

Your message dated Sun, 18 May 2025 08:47:23 +0200
with message-id <a4911d23-eded-49fa-af5b-67be56fbdb25@debian.org>
and subject line Re: Bug#1104335: britney/debci: sometimes lists a non-regression fail as a regression
has caused the Debian Bug report #1104335,
regarding britney/debci: sometimes lists a non-regression fail as a regression
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.)


-- 
1104335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104335
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
The testing excuses list sometimes shows an autopkgtest as 'Regression', with the reference link going to an old (often old enough that the log is no longer available) passing migration-reference, when a newer migration-reference exists and failed (i.e. when the failure is not actually a regression).
In all the cases I've noticed, this happened on only one architecture, even when the underlying 'reference used to pass, now fails' condition exists on more than one architecture.
Instances I've noticed recently are r-bioc-keggrest/amd64 #1104334 blocking r-base, pique/(I've forgotten which architecture) blocking r-base, and r-cran-plotly/riscv64 (listing https://ci.debian.net/packages/r/r-cran-plotly/testing/riscv64/58034134/ as the reference) blocking r-cran-testthat. (The fact that these are all R packages is probably because that's where I've been looking recently, *not* a property of the bug itself. This is not an unblock request, as none of those are otherwise ready.)
Workaround: Retrying the _reference_ test (using the link on the testing excuses page) makes it stop counting as a regression. Waiting *may* also do so.
--- End Message ---
--- Begin Message --- 
Hi,

On 01-05-2025 12:19, Paul Gevers wrote:
The fix will work for new data coming in, but not for data in the cache. Hitting the retry button should solve these issues. 


This problem should be fixed by now.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: