Hi,
I have addressed this with: https://review.openstack.org/15345
Have a good week.
Thanks
Gary
On 11/03/2012 12:08 PM, Gary Kotton wrote:
On 11/02/2012 09:25 PM, Robert Kukura wrote:
While trying to test a patch as part of my review day today, I
discovered tox is not working as it used to on master. I always search
for the strings "ERROR" and "FAIL" in the tox output to see whether
anything unexpected occurred and now I'm seeing lots of log output,
including quite a few lines containing "ERROR".
This seems to have been introduced by "Change I5adf72e6: Use openstack
common log to do logging." at https://review.openstack.org/#/c/15034/.
Compare the jenkins log from the merge before this at
http://logs.openstack.org/15019/2/gate/gate-quantum-python27/1987/console.html.gz
with the log from this merge at
http://logs.openstack.org/15034/4/gate/gate-quantum-python27/1988/console.html.gz.
I'm not very familiar with how tox works. Is there any way we could get
tox to once again suppress the log output unless a test actually fails,
which is what it seemed to do in the past? Jenkins doesn't seem to care,
but I think the old behavior helps developers and reviewers more easily
notice when things go wrong.
Note that run_tests.sh still seems to work normally.
-Bob
Hi,
I have also seen the problem and opened a bug -
https://bugs.launchpad.net/quantum/+bug/1074431
Thanks
Gary
--
Mailing list: https://launchpad.net/~quantum-core
Post to : [email protected]
Unsubscribe : https://launchpad.net/~quantum-core
More help : https://help.launchpad.net/ListHelp