Comment 1 for bug 409688

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 409688] [NEW] run_bzr gives a poor message when a blackbox test fails

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> Public bug reported:
>
> Example:
>
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/home/mbp/bzr/409684-cherrypick/bzrlib/tests/blackbox/test_merge.py", line 387, in test_directive_cherrypick
> out, err = self.run_bzr('merge -d target directive')
> AssertionError: Unexpected return code
> not equal:
> a = 0
> b = 1
>
> This is true but not very helpful. It would be nice if the test failure
> error included the error message from the underlying bzr command - there
> typically is one. It's not very urgent because the error typically is
> visible (along with a lot of other stuff) in the test log.
>
> ** Affects: bzr
> Importance: Low
> Status: Confirmed
>

So yeah, it *is* in the log, but it is hard to find. The log also
usually has the traceback, which is often just as important. I've often
found it a bit harder to debug than normal tests, though, because the
information I'm looking for isn't where I expect to find it.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkp64pMACgkQJdeBCYSNAAOZaQCeP4y46ctNm3PL7SsesHqIM1cq
gcAAnAws7iOvD9bdx1RTxiIvn7OvNeP/
=YEWw
-----END PGP SIGNATURE-----