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

Julian Gilbey <[email protected]>
Newsgroups gmane.linux.debian.devel.quality-assurance
Message-ID <Z0g_S1JrOOBDeB_l__15486.3109857374$1732788224$gmane$org@d-and-j.net>
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 reassign).
> 
> We make the results available with a cron job which runs at :30, so results
> should be available to any consumer within 20 minutes (britney2 typically
> takes 10 minutes and starts at :00).
> 
> Unless the master node of ci.d.n couldn't deliver the results when requested
> by britney1, or if britney1/britney2 crashed, or the cron job failed,
> there's not much we can do to speed up from our side.
> 
> 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 britney1/britney2 after 3 days, and showed no signs of ever
transferring.)

Best wishes,

   Julian
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.