[openstack-dev] [infra][neutron]SystemExit() vs sys.exit()?
Paul Michali (pcm)
pcm at cisco.com
Fri May 2 10:14:36 UTC 2014
Ah, I looked in .testrepository and there was information on the failure:
Content-Type: text/x-traceback;charset="utf8",language="python"
traceback
114
Traceback (most recent call last):
File "neutron/tests/unit/pcm/test_pcm.py", line 34, in test_using_SystemExit
self.assertIsNone(using_SystemExit())
File "neutron/tests/unit/pcm/test_pcm.py", line 25, in using_SystemExit
raise SystemExit("ouch")
SystemExit: ouch
0
]
Great! That was my big concern, I would run tox and it would show failures with just process-returncode and I couldn’t figure out where the problem occurred. I forgot about the .testrepository files. At least now I can figure out what causes those types of failures, which I do see occasionally.
Thanks!
PCM (Paul Michali)
MAIL …..…. pcm at cisco.com<mailto:pcm at cisco.com>
IRC ……..… pcm_ (irc.freenode.com<http://irc.freenode.com>)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
On May 1, 2014, at 2:57 PM, Yuriy Taraday <yorik.sar at gmail.com<mailto:yorik.sar at gmail.com>> wrote:
On Thu, May 1, 2014 at 10:41 PM, Paul Michali (pcm) <pcm at cisco.com<mailto:pcm at cisco.com>> wrote:
======================================================================
FAIL: process-returncode
tags: worker-1
----------------------------------------------------------------------
Binary content:
traceback (test/plain; charset="utf8")
======================================================================
FAIL: process-returncode
tags: worker-0
----------------------------------------------------------------------
Binary content:
traceback (test/plain; charset="utf8")
process-returncode failures means that child process (subunit one) exited with nonzero code.
It looks like there was some traceback, but it doesn’t show it. Any ideas how to get around this, as it makes it hard to troubleshoot these types of failures?
Somehow traceback got MIME type "test/plain". I guess, testr doesn't push this type of attachments to the screen. You can try to see what's there in .testrepository dir but I doubt there will be anything useful there.
I think this behavior is expected. Subunit process gets terminated because of uncaught SystemExit exception and testr reports that as an error.
--
Kind regards, Yuriy.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140502/6883303e/attachment-0001.html>
More information about the OpenStack-dev
mailing list