Bug#1030991: lintian: checking intel-mkl takes 18 hours
Control: tag -1 + confirmed
Hi Andreas,
Andreas Beckmann wrote:
> Checking intel-mkl (pre-built binaries in non-free) with lintian is very
> slow. A full build (i.e. source+all+any) on amd64 takes nearly 18 hours
> to check with
> lintian -i -E -L ">=pedantic" -v intel-mkl_2020.4.304-4_amd64.changes
> on my local machine (8 cores, 64 GB, tmpfs on /tmp, storage on nvme).
Thanks for that bug report. Knowing such examples to test is always
good to know. Performance is one thing we managed to get much better
in the past ¾ year or so, especially thanks to Bastien. But there is
obviously (and not only known since this bug report) place for
improvement. :-)
> I don't know where all the time is spent ...
Well, 549 MB of source package... :-)
I'll check if --perf-debug brings up anything helpful. Well, yes, but
I would have gathered that otherwise, too:
Warning in processable ../libmkl-threading-dev_2020.4.304-4_amd64.deb:
MLDBM error: Second level tie failed, "No space left on device" at
/usr/share/perl5/MLDBM.pm line 144.
So, new try.
>From the output I already see that these checks took quite a while
(that's where output stopped for quite a while:
Running check: debian/control/field/rules-requires-root on source:intel-mkl_2020.4.304-4 ...
Running check: documentation/manual on binary:libmkl-meta-threading_2020.4.304-4_amd64 ...
Anyway, will wait what I get at the end. Everything with "done (0."
can be ignored. :-)
Anyway, tagging as confirmed as I can already see now that it will
take a while. :-)
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Reply to: