New issue 466: IOError when writing --junitxml report
https://bitbucket.org/hpk42/pytest/issue/466/ioerror-when-writing-junitxml-report

Steven R:

**Version**: pytest-2.4.2-py2.7
**Related bug 1**: 
https://bitbucket.org/hpk42/pytest/issue/271/ioerror-when-writing-junitxml-report-when
**Related bug 2**: 
https://bitbucket.org/hpk42/pytest/issue/173/pytest-fails-when-writing-junit-style-test
**Frequency**: Intermittent 1/20
**Note**: This may be related to new file or folder structure on clean systems. 
 I'm only seeing this on the initial runs of the test on new systems.

Traceback (most recent call last):
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\runpy.py",
 line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\runpy.py",
 line 72, in _run_code
    exec code in run_globals
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\pytest.py",
 line 10, in <module>
    raise SystemExit(pytest.main())
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\config.py",
 line 19, in main
    exitstatus = config.hook.pytest_cmdline_main(config=config)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\core.py",
 line 368, in __call__
    return self._docall(methods, kwargs)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\core.py",
 line 379, in _docall
    res = mc.execute()
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\core.py",
 line 297, in execute
    res = method(**kwargs)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\main.py",
 line 111, in pytest_cmdline_main
    return wrap_session(config, _main)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\main.py",
 line 104, in wrap_session
    exitstatus=session.exitstatus)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\core.py",
 line 368, in __call__
    return self._docall(methods, kwargs)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\core.py",
 line 379, in _docall
    res = mc.execute()
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\core.py",
 line 297, in execute
    res = method(**kwargs)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\terminal.py",
 line 325, in pytest_sessionfinish
    __multicall__.execute()
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\core.py",
 line 297, in execute
    res = method(**kwargs)
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\site-packages\pytest-2.4.2-py2.7.egg\_pytest\junitxml.py",
 line 209, in pytest_sessionfinish
    logfile = py.std.codecs.open(self.logfile, 'w', encoding='utf-8')
  File 
"C:\Jenkins\workspace\Test-Stress-ServerRegression\sw\tools\win32\python\275\lib\codecs.py",
 line 881, in open
    file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 2] No such file or directory:  
'C:\\Jenkins\\workspace\\Test-Stress-ServerRegression\\Logs\\project_stress_test_results.xml'



_______________________________________________
pytest-commit mailing list
pytest-commit@python.org
https://mail.python.org/mailman/listinfo/pytest-commit

Reply via email to