On 16.01.2016 19:31, Sébastien Villemot wrote:
Le samedi 16 janvier 2016 à 19:24 +0100, Matthias Klose a écrit :
On 16.01.2016 18:00, Sébastien Villemot wrote:
I was aware of the failure but decided to nevertheless add that
> testsuite as an autopkgtest, in order to make the test failures
m
Le samedi 16 janvier 2016 à 19:24 +0100, Matthias Klose a écrit :
> On 16.01.2016 18:00, Sébastien Villemot wrote:
> > 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.
>
> I'll never understand why
On 16.01.2016 18:00, Sébastien Villemot wrote:
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.
I'll never understand why people do that ... once Debian adds succeeding autopkg
tests as a requiremen
Processing control commands:
> severity -1 normal
Bug #811191 [src:lapack] [regression] lapack 3.6.0 fails the testsuite
Severity set to 'normal' from 'important'
> retitle -1 some test fails in LAPACK testsuite
Bug #811191 [src:lapack] [regression] lapack 3.6.0 fails the testsuite
Changed Bug tit
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.
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
