run_tests.py exits with 0 even if tests failed
Bug #740109 reported by
Jelmer Vernooij
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Meliae |
Fix Released
|
Medium
|
Jelmer Vernooij |
Bug Description
the testsuite always seems to return 0 at the moment, even if there were failing or errorring tests.
this makes it harder to script running the testsuite in e.g. packaging scripts.
Related branches
lp:~jelmer/meliae/tests-exitcode
- John A Meinel: Approve
-
Diff: 13 lines (+2/-1)1 file modifiedmeliae/tests/__init__.py (+2/-1)
Changed in meliae: | |
status: | New → In Progress |
assignee: | nobody → Jelmer Vernooij (jelmer) |
Changed in meliae: | |
milestone: | none → 0.4 |
Changed in meliae: | |
status: | In Progress → Fix Committed |
importance: | Undecided → Medium |
Changed in meliae: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 3/22/2011 12:07 PM, Jelmer Vernooij wrote:
> Public bug reported:
>
> the testsuite always seems to return 0 at the moment, even if there were
> failing or errorring tests.
>
> this makes it harder to script running the testsuite in e.g. packaging
> scripts.
>
> ** Affects: meliae
> Importance: Undecided
> Assignee: Jelmer Vernooij (jelmer)
> Status: In Progress
>
> ** Changed in: meliae
> Status: New => In Progress
>
> ** Changed in: meliae
> Assignee: (unassigned) => Jelmer Vernooij (jelmer)
>
> ** Branch linked: lp:~jelmer/meliae/tests-exitcode
>
We may just want to change it to use "testtools.run" if that does the
right thing.
I'm not wedded to the test runner. Though I like having optional -v and
- --one and regex matching.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
IhT0ACgkQJdeBCY SNAAM47gCglTBqw c0hJpg7gQKH22JQ rMcg BDP++nuMwwH727C l8
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAk2
wM4AoM5fjcNN74g
=XTAH
-----END PGP SIGNATURE-----