The build log scanner reports stale data for ncurses from the 20190803-1
version[1].  The problems reported there have been fixed[2] in the
20191019-1 upload, yet the tracker keeps complaining.

Either the new ncurses version has not been scanned at all, despite
having been uploaded 19 days ago, or the information has been discarded,
perhaps because blhc produced no output at all for the new packages (as
desired).


1. https://qa.debian.org/bls/packages/n/ncurses.html
2. https://salsa.debian.org/debian/ncurses/commit/b63259877ad51c393461e45597335f5c978ed9f4

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 scanning the build logs, e.g. to see how quickly a
report is generated relative to build logs becoming available, and how often the
scans fail (which would explain staleness in reports)

thanks,
Serafeim

ps. please cc me on replies, I'm not subscribed in debian-qa@

bls is deployed in wuiet.d.o (aka buildd.d.o) directly under brlink's
home directory.

Since Bernhard is fairly inactive nowadays the whole thing bitrotted a
bit, and since it was deployed so... "privately" (instead of, saying,
using the ~qa user in wuiet - which does not exit, but it would be
trivial to have it created by DSA) it also makes one just not want to
even look at it.

thanks, that's very helpful! I'll discuss with DSA the best way forward.