Control: severity -1 normal Control: retitle -1 some test fails in LAPACK testsuite
Le samedi 16 janvier 2016 à 17:29 +0100, Matthias Klose a écrit : > Package: src:lapack > Version: 3.6.0-2 > Severity: important > Tags: sid stretch > > Regressed compared to 3.5.0. > > According to > https://ci.debian.net/packages/l/lapack/unstable/amd64/ > > lapack fails the lapack-testsuite, but is very terse about what > exactly failed: > > adt-run [11:49:05]: test lapack-testsuite: [----------------------- > Total errors: 2 > adt-run [11:50:15]: test lapack-testsuite: -----------------------] > adt-run [11:50:15]: test lapack-testsuite: - - - - - - - - - - > results - - - - > - - - - - - > lapack-testsuite FAIL non-zero exit status 1 > adt-run [11:50:15]: @@@@@@@@@@@@@@@@@@@@ summary > xerbla-fortran PASS > xerbla-c PASS > blas-testsuite PASS > lapack-testsuite FAIL non-zero exit status 1 > > According to http://autopkgtest.ubuntu.com/packages/l/lapack/ > it fails on armhf and i386 as well The autopkgtest lapack-testsuite has been added in revision 3.6.0-1, sot he failure is technically not a regression. Actually the testsuite hasalways been failing on some arches (but only a few tests out of several thousands), but the testsuite was only run a buildtime and the failure was not made fatal, to avoid FTBFSes. So I'm adjusting the severity and the title. I was aware of the failure but decided to nevertheless add that testsuite as an autopkgtest, in order to make the test failures more visible. On amd64 there is a failure in a single test (out of several thousands) that has been reported upstream. For other archs more investigation is needed. Maybe I could make the autopkgtest more verbose by printing the test summary. But that summary can be seen anyways in the build log (since the testsuite is also run at build time). -- .''`. Sébastien Villemot : :' : Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594
signature.asc
Description: This is a digitally signed message part
