Bug#1088254: tracker.debian.org: seems to be severely lagging behind ci.debian.net for (at least) some packages

2024-11-28 Thread Paul Gevers
Hi, On 11/28/24 08:32, Raphael Hertzog wrote: I'm tempted to close it, but I'll CC debian-release to see if someone managing britney has any clue... (I guess release.debian.org would be the right package if we wanted to reassign). We make the results available with a cron job which runs at :30

Bug#1088254: tracker.debian.org: seems to be severely lagging behind ci.debian.net for (at least) some packages

2024-11-28 Thread Paul Gevers
Hi, On 11/28/24 11:00, Julian Gilbey wrote: We had issues on ci.d.n last week, which also led to britney1 bailing out because there were no results. I guess it was those problems that caused the issue, then. (Just to clarify, in this case, the results hadn't been transferred from ci.d.n to br

Bug#1088254: tracker.debian.org: seems to be severely lagging behind ci.debian.net for (at least) some packages

2024-11-28 Thread Julian Gilbey
On Thu, Nov 28, 2024 at 09:45:41AM +0100, Paul Gevers wrote: > Hi, > > On 11/28/24 08:32, Raphael Hertzog wrote: > > I'm tempted to close it, but I'll CC debian-release to see if someone > > managing britney has any clue... (I guess release.debian.org would be the > > right package if we wanted to

Bug#1088254: tracker.debian.org: seems to be severely lagging behind ci.debian.net for (at least) some packages

2024-11-28 Thread NoisyCoil
Package: tracker.debian.org Followup-For: Bug #1088254 X-Debbugs-Cc: noisyc...@tutanota.com Hi, I had a similar experience to Julian's. bindgen 0.70.1-2 was uploaded on November 22 together with a large number of rdeps. Most tests were run by November 24 at the latest (I checked them manually on

Bug#1088254: tracker.debian.org: seems to be severely lagging behind ci.debian.net for (at least) some packages

2024-11-28 Thread Julian Gilbey
Hi Paul, On Thu, Nov 28, 2024 at 12:44:15PM +0100, Paul Gevers wrote: > On 11/28/24 11:00, Julian Gilbey wrote: > > > We had issues on ci.d.n last week, which also led to britney1 bailing out > > > because there were no results. > > > > I guess it was those problems that caused the issue, then.