This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients steve.dower, terry.reedy, tim.golden, zach.ware
Date 2015-05-13.21:47:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431553670.83.0.456032288115.issue24181@psf.upfronthosting.co.za>
In-reply-to
Content
In console: pcbuild/win32/python_d.exe -m test -j6
...
[393/395/1] test_fileio
Traceback (most recent call last):
  File "F:\Python\dev\35\lib\runpy.py", line 170, in _run_module_as_main
    "__main__", mod_spec)
  File "F:\Python\dev\35\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "F:\Python\dev\35\lib\test\__main__.py", line 3, in <module>
    regrtest.main_in_temp_cwd()
  File "F:\Python\dev\35\lib\test\regrtest.py", line 1564, in main_in_temp_cwd
    main()
  File "F:\Python\dev\35\lib\test\regrtest.py", line 738, in main
    raise Exception("Child error on {}: {}".format(test, result[1]))
Exception: Child error on test_fileio: Exit code 2147483651

In crash box: Debug assertion failed
/dd/vctools/crt_bld/self_x86/crt/src/chsize.c
line 56  _osfile(desfile) & FOPEN

By leaving box alone, all but about 4 tests finished.  When clicked on button, fileio message appeared. On previous run, click as soon as box appeared, and console window frooze much sooner, with just half of tests run.

There were also 'Python_d.exe has stopped working' messages, but same true with 3.4 tests, which finished.
History
Date User Action Args
2015-05-13 21:47:50terry.reedysetrecipients: + terry.reedy, tim.golden, zach.ware, steve.dower
2015-05-13 21:47:50terry.reedysetmessageid: <1431553670.83.0.456032288115.issue24181@psf.upfronthosting.co.za>
2015-05-13 21:47:50terry.reedylinkissue24181 messages
2015-05-13 21:47:50terry.reedycreate