[openstack-dev] [stestr?][tox?][infra?] Unexpected success isn't a failure

Chris Dent cdent+os at anticdent.org
Tue Jul 10 09:16:37 UTC 2018

On Mon, 9 Jul 2018, Matthew Treinish wrote:

> It's definitely  a bug, and likely a bug in stestr (or one of the lower level
> packages like testtools or python-subunit), because that's what's generating
> the return code. Tox just looks at the return code from the commands to figure
> out if things were successful or not. I'm a bit surprised by this though I
> thought we covered the unxsuccess and xfail cases because I would have expected
> cdent to file a bug if it didn't. Looking at the stestr tests we don't have
> coverage for the unxsuccess case so I can see how this slipped through.

This was reported on testrepository some years ago and a bit of
analysis was done: https://bugs.launchpad.net/testrepository/+bug/1429196

So yeah, I did file a bug but it fell off the radar during those
dark times.

Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent

More information about the OpenStack-dev mailing list