When attempting to build a new tool for Tempest, I found that my python
syntax errors were being completely eaten. After 2 days of debugging I
found that oslo log.py does the following *very unexpected* thing.
- replaces the sys.excepthook with it's own function
- eats the execption traceback
On Wed, May 28, 2014 at 10:38 AM, Sean Dague s...@dague.net wrote:
When attempting to build a new tool for Tempest, I found that my python
syntax errors were being completely eaten. After 2 days of debugging I
found that oslo log.py does the following *very unexpected* thing.
- replaces the
On 05/28/2014 11:39 AM, Doug Hellmann wrote:
On Wed, May 28, 2014 at 10:38 AM, Sean Dague s...@dague.net wrote:
When attempting to build a new tool for Tempest, I found that my python
syntax errors were being completely eaten. After 2 days of debugging I
found that oslo log.py does the
List (not for usage questions)
openstack-dev@lists.openstack.org
Date: May 28, 2014 at 08:50:25
To: openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Oslo logging eats system level tracebacks by
default
On 05/28/2014 11:39 AM, Doug Hellmann wrote
+1 from me.
On Wed, May 28, 2014 at 11:49 AM, Jay Pipes jaypi...@gmail.com wrote:
On 05/28/2014 11:39 AM, Doug Hellmann wrote:
On Wed, May 28, 2014 at 10:38 AM, Sean Dague s...@dague.net wrote:
When attempting to build a new tool for Tempest, I found that my python
syntax errors were being
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Oslo logging eats system level tracebacks by
default
+1 Providing service crashing information is very valuable. In general we need
to provide as much information about why the service exited
(critically/traceback
