[Bug 1075612] Re: coreutils autopkgtests do not fail correctly when a test fails
Launchpad Bug Tracker
1075612 at bugs.launchpad.net
Wed Nov 7 18:53:56 UTC 2012
This bug was fixed in the package coreutils - 8.13-3.2ubuntu4
---------------
coreutils (8.13-3.2ubuntu4) raring; urgency=low
[ Paul Larson ]
* Fix debian/tests/upstream: Make the test script count the number of test
failures, declare them at the end of the test run, and exit with the
number of failed tests. (LP: #1075612)
[ Martin Pitt ]
* debian/tests/upstream: Drop du/bigtime test, does not work in our test
environment.
-- Martin Pitt <martin.pitt at ubuntu.com> Wed, 07 Nov 2012 15:51:30 +0100
** Changed in: coreutils (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1075612
Title:
coreutils autopkgtests do not fail correctly when a test fails
Status in “coreutils” package in Ubuntu:
Fix Released
Bug description:
When running the autopkgtests for coreutils I noticed that some tests
were getting marked as FAIL but the script was passing and exiting
with 0 regardless. The script is running with || { do some other
things that won't fail } so the set -e had no effect. I'm not sure
what the recommended behaviour is for autopkgtests, but in general I
usually like to see all the test failures in one go, unless there was
something catastrophically wrong with the whole thing running. So I
left the -e in, but updated it a bit to count the failures and exit
with the total count.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1075612/+subscriptions
More information about the foundations-bugs
mailing list