djsundog/circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a6400fb08a
circuitpython/tests/misc/sys_settrace_loop.py.exp

73 lines
3.2 KiB
Plaintext
Raw Normal View History

tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: call
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:41
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:43
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:44
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:45
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:44
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:45
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:44
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:45
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:44
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:45
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:46
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
test_for_loop 3
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:49
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:50
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:51
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:53
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:52
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:53
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:52
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:53
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:52
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:53
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
### trace_handler::main event: line
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:54
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
test_while_loop 3
### trace_handler::main event: return
tests/misc/sys_settrace: Make test output independent of invoked path. The original logic of reducing a full path to a relative one assumes "tests/misc" is in the filename which is limited in usage: it never works for CPython on Windows since that will use a backslash as path separator, and also won't work when the filename is a path not relative to the tests directory which happens for example in the common case of running "./run-tests -d misc". Fix all cases by printing only the bare filename, which requires them all to start with sys_settrace_ hence the renaming.
2020-12-15 05:54:34 -05:00
0: @__main__:test_loop => sys_settrace_loop.py:54
1: @__main__:<module> => sys_settrace_loop.py:58
tests: Add tests for sys.settrace feature.
2019-08-14 10:11:25 -04:00
Total traces executed: 23
Reference in New Issue Copy Permalink