New submission from Zachary Ware: In test_winsound, PlaySoundTest.test_alias_fallback has been commented out for quite some time but has been reported as 'ok' ever since. Does anyone know what the current status of the test is? Should it still be skipped (explicitly)? Should it be marked as an expected failure? Would it be dangerous to enable? My own testing shows it to be harmless on my machine, but my range of test configurations is sorely limited at present. My own suggestion is to mark it as an expected failure (or just enable it wholesale, and mark it if it does prove flaky) and see what the buildbots make of it, but I don't want to do that if it could cause anything worse than an exception.
Thoughts? ---------- components: Tests, Windows messages: 202887 nosy: brian.curtin, serhiy.storchaka, tim.golden, zach.ware priority: normal severity: normal status: open title: Silently skipped test in test_winsound type: behavior versions: Python 2.7, Python 3.3, Python 3.4 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19595> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
