Package: parsinsert Version: 1.04-4 Severity: important User: [email protected] Usertags: origin-ubuntu disco
Dear maintainers,
The parsinsert package passed its autopkgtests in Ubuntu on armhf as of
1.04-3; but with the 1.04-4 update, the tests now fail:
[...]
Rank Matches:
_________Precision________ __________Recall__________
Domain: 957 938 ( 98.01%) 938 957 ( 98.01%)
Phylum: 957 83 ( 8.67%) 83 957 ( 8.67%)
Class: 957 83 ( 8.67%) 83 957 ( 8.67%)
Order: 915 0 ( 0.00%) 0 915 ( 0.00%)
Family: 876 0 ( 0.00%) 0 876 ( 0.00%)
Genus: 706 0 ( 0.00%) 0 706 ( 0.00%)
Species: 53 0 ( 0.00%) 0 53 ( 0.00%)
Insert Time = 82, 42014 per hour
Process Completed: 102 sec
incorrect result
autopkgtest [23:16:43]: test run-unit-test: -----------------------]
autopkgtest [23:16:46]: test run-unit-test: - - - - - - - - - - results - - -
- - - - - - -
run-unit-test FAIL non-zero exit status 1
[...]
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/armhf/p/parsinsert/20190206_231724_739fb@/log.gz)
Investigation suggests this is a regression caused by toolchain changes that
have resulted in a broken armhf binary build in 1.04-4: there are clearly no
changes to the testsuite between -3 and -4, the -3 binary still passes the
testsuite with current libraries, and a no-change rebuild of -3 fails the
same way.
Since Debian does not run autopkgtests on !amd64, I would strongly recommend
running these tests at build time as well, to avoid shipping broken binaries
on other architectures.
Note that these tests also fail on arm64, i386, and ppc64el in Ubuntu,
suggestings the packages are also broken there, but none of these are
regressions.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
[email protected] [email protected]
signature.asc
Description: PGP signature
