You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the junitxml flag, it outputs all the traceback, stderr and stdout into Jenkins' stacktrace. The stderr and stdout should be put into and respectively instead of everything in . This will make the xml output more compatible with Jenkins and plugins.
Original comment byBrian O'Neill (BitBucket: sfbrian, GitHub: sfbrian):
Here is an example of Jenkins using stdout. We made a hack to put all the stdout and stderr into Jenkins' stdout to get a quick fix: https://skitch.com/boneill428/fj8q2/stdout
Our hack was:
sed -i -e 's###g'
-e 's#------------------------------- Captured stdout --------------------------------##g'
results.xml
? should give you pytest-2.1.1.dev2 at least (see py.test -v) and better xml files. I wasn't 100% sure how the xml format looks like - if there are issues, please provide an exmaple xml file.
self = Use exit() or Ctrl-D (i.e. EOF) to exit, code = None
def __call__(self, code=None):
# Shells like IDLE catch the SystemExit, but listen when their
# stdin wrapper is closed.
try:
sys.stdin.close()
except:
pass
Activity
pytestbot commentedon Jul 6, 2011
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian):
This is who reported the bug in case you have more questions.
pytestbot commentedon Jul 8, 2011
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):
i see.
curious, can you point to a Jenkins page that makes use of system-out/system-err?
pytestbot commentedon Jul 11, 2011
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian):
Here is an example of Jenkins using stdout. We made a hack to put all the stdout and stderr into Jenkins' stdout to get a quick fix: https://skitch.com/boneill428/fj8q2/stdout
Our hack was:
sed -i -e 's###g'
-e 's#------------------------------- Captured stdout --------------------------------##g'
results.xml
pytestbot commentedon Jul 12, 2011
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):
fix #59: provide better Jenkins stdout and stderr sections
pytestbot commentedon Jul 12, 2011
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):
could you verify it works for you by installing:
pip install -i http://pypi.testrun.org -U pytest
? should give you pytest-2.1.1.dev2 at least (see py.test -v) and better xml files. I wasn't 100% sure how the xml format looks like - if there are issues, please provide an exmaple xml file.
thanks,
holger
pytestbot commentedon Jul 12, 2011
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian):
Thanks for the fix Holger. One minor change is needed. The format should be:
**_System Out**_ **_System Error**_{{{
_Traceback_
}}}
Currently the format is wrapped in the failure tag instead at the same level as failure:
**_Trackback**_ **_System Out**_{{{
Example:
{{{
self = <general.GeneralTest testMethod=test_help_page>
> exit()
general.py:84:
self = Use exit() or Ctrl-D (i.e. EOF) to exit, code = None
> raise SystemExit(code)
E SystemExit: None
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site.py:334: SystemExit
SauceOnDemandSessionID=null job-name=foo
2011-07-12 15:20:49,608 - logger - INFO - Sauce Labs Video: https://saucelabs.com/jobs/null
2011-07-12 15:20:49,608 - logger - INFO - test_help_page Started
2011-07-12 15:20:53,392 - logger - INFO - test_help_page Finished
}}}
pytestbot commentedon Jul 13, 2011
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):
thanks, i think i fixed it. See "pip install -i http://pypi.testrun.org -U pytest" (version dev3 now)
pytestbot commentedon Jul 13, 2011
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian):
Looks great! Thanks for the fix. You rock!
Don't remove the single trailing comma from square bracket indexing
Mention fix for pytest-dev#59
Fix For Pytest 3.1.0+ (pytest-dev#59)