[issue32733] test_coroutines is failed when run with -We

2018-02-01 Thread Nathaniel Smith
Nathaniel Smith added the comment: Thanks! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32733] test_coroutines is failed when run with -We

2018-02-01 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Thank you Nathaniel. And congratulate with getting core developer status! -- ___ Python tracker

[issue32733] test_coroutines is failed when run with -We

2018-02-01 Thread Nathaniel Smith
Nathaniel Smith added the comment: New changeset 709f6ad7f84855ebdbe3e7702571b0e1447b885b by Nathaniel J. Smith (Miss Islington (bot)) in branch '3.7': bpo-32733: Make test_coroutines robust against -Werror (GH-5487) (GH-5490)

[issue32733] test_coroutines is failed when run with -We

2018-02-01 Thread miss-islington
Change by miss-islington : -- pull_requests: +5320 ___ Python tracker ___

[issue32733] test_coroutines is failed when run with -We

2018-02-01 Thread Nathaniel Smith
Nathaniel Smith added the comment: New changeset 2efb9735899c7c642f3e75a121af82b1679577d3 by Nathaniel J. Smith in branch 'master': bpo-32733: Make test_coroutines robust against -Werror (GH-5487)

[issue32733] test_coroutines is failed when run with -We

2018-02-01 Thread Nathaniel Smith
Change by Nathaniel Smith : -- keywords: +patch pull_requests: +5317 stage: -> patch review ___ Python tracker ___

[issue32733] test_coroutines is failed when run with -We

2018-01-31 Thread Yury Selivanov
Yury Selivanov added the comment: Or to use assertWarnsRegex -- ___ Python tracker ___

[issue32733] test_coroutines is failed when run with -We

2018-01-31 Thread Yury Selivanov
Yury Selivanov added the comment: I think assertWarns just handles it. Maybe the test should be converted to use it? -- ___ Python tracker

[issue32733] test_coroutines is failed when run with -We

2018-01-31 Thread Nathaniel Smith
Nathaniel Smith added the comment: Ok, yeah, that's a test that a warning is emitted, which fails when the warning is converted into an error instead. Need to normalize the warnings filter settings inside that test, I guess. How does this not cause the same problem for every

[issue32733] test_coroutines is failed when run with -We

2018-01-31 Thread Yury Selivanov
Yury Selivanov added the comment: Nathaniel, this seems to be related to coro-origin-tracking. -- nosy: +njs ___ Python tracker

[issue32733] test_coroutines is failed when run with -We

2018-01-31 Thread Serhiy Storchaka
New submission from Serhiy Storchaka : $ ./python -We -m test test_coroutines Run tests sequentially 0:00:00 load avg: 0.29 [1/1] test_coroutines Exception ignored in: .corofn at 0x7fc5fc692cb8> Traceback (most recent call last): File