Cron lintian/reporting/harness -i

Warning: unable to close filehandle properly: No space left on device during global destruction.

Bug#924449: lintian: Periodic "out of disk space" errors from lindsay.d.o

On Fri, 5 Jul 2019, Felix Lechner wrote: > Hi François, > > On Fri, Jul 5, 2019 at 2:03 AM Francois Gouget wrote: > > > > I'm also running into "out of disk space" errors caused by Lintian. > > These happen when I check a 240 MB package > > Would you please provide a link to this package?

Build failed in Jenkins: lintian-tests_sid #3767

See Changes: [lamby] Add missing ";". [lamby] Add 4.4.0 as a known Standards-Version. -- [...truncated 311.76 KB...] Building in

lintian.d.o issues

Hi, As I mentioned on #debian-qa, I made a few changes on lindsay (the machine on which the archive-wide Lintian runs happen), after it was pointed out that it hadn't updated for a while - since late April, in fact. The specific issue there turned out to be a missing import when

Bug#929729: lintian: \n in filenames cause "md5sum: ...: No such file or directory"

Hi Felix, […] > > … but this is clearly hacking around the problem and is likely > > incomplete. Storing the newline literally in the internal structure > > breaks other things that I can't immediately see/fix. > > I agree. I rewrote the collections using IO::Async (coming once buster > is out)

Bug#930487: lintian: speed up test suite CI

Hi Dmitry, On Sat, Jul 6, 2019 at 11:27 PM Dmitry Bogatov wrote: > > > I think the most common use-case is that I make some change — possibly > > extremely minor — in, say, checks/foo.pm and I want to re-run the > > testsuite to check that I've fixed whatever false-positive or edge-case > > in a

Cron lintian/reporting/harness --no-generate-reports -i

Warning: unable to close filehandle properly: No space left on device during global destruction.

Bug#930487: lintian: speed up test suite CI

@Felix I think, that your proposal of caching test binary package separately from test output would be improvement. Maybe it would even be "good enough". I will take a look (no promises made) into this direction. But ideally... [2019-07-04 18:00] "Chris Lamb" > I think the most common