Re: Trying to come back

On Fri, Jul 12, 2024 at 08:05:20AM -0400, Barry deFreese wrote: > I have read that but I'm not listed as emeritus (again, my fault). Oh, good point. That's also partially our fault as we are very slow in removing inactive people. So, formally, you won't have to go through the nm because -formall

Bug#944620: #944620: qa.debian.org: build log scanner reports stale data

On Tue, Jul 30, 2024 at 04:41:10PM +0200, Serafeim Zanikolas wrote: > looking at #944620, can somebody please share specifics of where/how the build > log scanner is deployed/scheduled, and whether its logs are available for > investigation? bls is deployed in wuiet.d.o (aka buildd.d.o) directly u

Processed: block 1002462 with 944620

Processing commands for cont...@bugs.debian.org: > block 1002462 with 944620 Bug #1002462 [tracker.debian.org] "build log checks report 1 warning" dated a year and 9 uploads ago 1002462 was not blocked by any bugs. 1002462 was not blocking any bugs. Added blocking bug(s) of 1002462: 944620 > than

Re: #944620: qa.debian.org: build log scanner reports stale data

hi Bernhard, qa folks, looking at #944620, can somebody please share specifics of where/how the build log scanner is deployed/scheduled, and whether its logs are available for investigation? https://qa.debian.org/bls links to package build logs, whereas I'm after the logs that are generated while