New submission from STINNER Victor:

The issue #23848 (change b114dbbe2d31) enhanced the faulthandler module to log 
Windows exceptions with the Python traceback. It uses 
AddVectoredExceptionHandler(1, callback) to register the callback.

Problem: test_winreg now logs a lot of "Windows exception: code 0x06ba" 
messages followed by traceback. It's error RPC_S_SERVER_UNAVAILABLE (1722): 
"The RPC server is unavailable". It doesn't seem like a fatal error, so I'm not 
sure that it's worth to log it.

Is it possible to check if an exception is a fatal error or not?

Or should we explicitly ignore *this* specific error?

Note: faulthandler must be enabled manually.

Example of trace:
http://buildbot.python.org/all/builders/AMD64%20Windows8%203.x/builds/1885/steps/test/logs/stdio
----
Windows exception: code 0x06ba

Current thread 0x00000500 (most recent call first):
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\test_winreg.py", line 
305 in test_dynamic_key
  File "D:\buildarea\3.x.bolen-windows8\build\lib\unittest\case.py", line 600 
in run
  File "D:\buildarea\3.x.bolen-windows8\build\lib\unittest\case.py", line 648 
in __call__
  File "D:\buildarea\3.x.bolen-windows8\build\lib\unittest\suite.py", line 122 
in run
  File "D:\buildarea\3.x.bolen-windows8\build\lib\unittest\suite.py", line 84 
in __call__
  File "D:\buildarea\3.x.bolen-windows8\build\lib\unittest\suite.py", line 122 
in run
  File "D:\buildarea\3.x.bolen-windows8\build\lib\unittest\suite.py", line 84 
in __call__
  File "D:\buildarea\3.x.bolen-windows8\build\lib\unittest\runner.py", line 176 
in run
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\support\__init__.py", 
line 1802 in _run_suite
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\support\__init__.py", 
line 1836 in run_unittest
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\test_winreg.py", line 
479 in test_main
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\libregrtest\runtest.py", 
line 162 in runtest_inner
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\libregrtest\runtest.py", 
line 115 in runtest
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\libregrtest\main.py", 
line 306 in run_tests_sequential
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\libregrtest\main.py", 
line 367 in run_tests
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\libregrtest\main.py", 
line 405 in main
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\libregrtest\main.py", 
line 446 in main
  File "D:\buildarea\3.x.bolen-windows8\build\lib\test\libregrtest\main.py", 
line 468 in main_in_temp_cwd
  File "D:\buildarea\3.x.bolen-windows8\build\PCbuild\..\lib\test\regrtest.py", 
line 39 in <module>
----

----------
components: Tests, Windows
messages: 262263
nosy: haypo, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: test_winreg now logs "Windows exception: code 0x06ba" on Python 3.6
versions: Python 3.6

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26622>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to