MetaTrader5-Docker-Image/config.old-32bit/.wine/drive_c/Program Files (x86)/Python39-32/Lib/test/crashers
bast c5c0d42eac
All checks were successful
MT5 Helm GitOps Deploy / build-and-deploy (push) Has been skipped
using broker mt5
2026-11-06 01:29:29 +01:00
..
bogus_code_obj.py using broker mt5 2026-11-06 01:29:29 +01:00
gc_inspection.py using broker mt5 2026-11-06 01:29:29 +01:00
infinite_loop_re.py using broker mt5 2026-11-06 01:29:29 +01:00
mutation_inside_cyclegc.py using broker mt5 2026-11-06 01:29:29 +01:00
README using broker mt5 2026-11-06 01:29:29 +01:00
recursive_call.py using broker mt5 2026-11-06 01:29:29 +01:00
trace_at_recursion_limit.py using broker mt5 2026-11-06 01:29:29 +01:00
underlying_dict.py using broker mt5 2026-11-06 01:29:29 +01:00

This directory only contains tests for outstanding bugs that cause the
interpreter to segfault.  Ideally this directory should always be empty, but
sometimes it may not be easy to fix the underlying cause and the bug is deemed
too obscure to invest the effort.

Each test should fail when run from the command line:

	./python Lib/test/crashers/weakref_in_del.py

Put as much info into a docstring or comments to help determine the cause of the
failure, as well as a bugs.python.org issue number if it exists.  Particularly
note if the cause is system or environment dependent and what the variables are.

Once the crash is fixed, the test case should be moved into an appropriate test
(even if it was originally from the test suite).  This ensures the regression
doesn't happen again.  And if it does, it should be easier to track down.

Also see Lib/test_crashers.py which exercises the crashers in this directory.
In particular, make sure to add any new infinite loop crashers to the black
list so it doesn't try to run them.