[issue36692] Unexpected stderr output from test_sys_settrace

[Nick Coghlan]

Nick Coghlan  added the comment:

I'm not, so I assume this got cleaned up somewhere along the way.

--
resolution:  -> out of date
stage: needs patch -> resolved
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36692] Unexpected stderr output from test_sys_settrace

[Irit Katriel]

Irit Katriel  added the comment:

I'm not seeing this output when I run the test. Are you still seeing it?

--
nosy: +iritkatriel
status: open -> pending

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36692] Unexpected stderr output from test_sys_settrace

[Philip Dye]

Philip Dye  added the comment:

Once consensus is reached, I would be happy to do the work.

--
nosy: +Philip Dye

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36692] Unexpected stderr output from test_sys_settrace

[hai shi]

hai shi  added the comment:

It looks like setstrace function trigger this codeline: 
https://github.com/python/cpython/blob/master/Modules/_asynciomodule.c#L2618

Looks we can use set_exception_handler() to catch this error, but i am not sure 
it is worth catching this error through adding  a extended exception hander.

so, Nick, what's your thought?

REF: 
https://github.com/python/cpython/blob/master/Lib/asyncio/base_events.py#L1627

--
nosy: +shihai1991

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36692] Unexpected stderr output from test_sys_settrace

[Nick Coghlan]

New submission from Nick Coghlan :

The test output from test_sys_settrace makes it look like a couple of the async 
tracing tests aren't cleaning up after themselves properly:

```
[ncoghlan@localhost cpython]$ ./python -m test test_sys_settrace
Run tests sequentially
0:00:00 load avg: 1.27 [1/1] test_sys_settrace
unhandled exception during asyncio.run() shutdown
task: ()> exception=RuntimeError("can't send non-None value to a 
just-started coroutine")>
RuntimeError: can't send non-None value to a just-started coroutine
unhandled exception during asyncio.run() shutdown
task: ()> exception=RuntimeError("can't send non-None value to a 
just-started coroutine")>
RuntimeError: can't send non-None value to a just-started coroutine

== Tests result: SUCCESS ==

1 test OK.

Total duration: 102 ms
Tests result: SUCCESS

```

If that output is actually expected as part of the test, it would be helpful if 
the test printed a message beforehand saying to expect it. Otherwise, it would 
be desirable for the test to clean up after itself and keep the messages from 
being displayed in the first place.

--
components: Tests
messages: 340608
nosy: asvetlov, ncoghlan, yselivanov
priority: low
severity: normal
stage: needs patch
status: open
title: Unexpected stderr output from test_sys_settrace
type: behavior
versions: Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com