This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients brian.curtin, serhiy.storchaka, tim.golden, zach.ware
Date 2013-11-14.21:00:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384462856.95.0.594659229823.issue19595@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2013-11-14 21:00:56zach.waresetrecipients: + zach.ware, tim.golden, brian.curtin, serhiy.storchaka
2013-11-14 21:00:56zach.waresetmessageid: <1384462856.95.0.594659229823.issue19595@psf.upfronthosting.co.za>
2013-11-14 21:00:56zach.warelinkissue19595 messages
2013-11-14 21:00:56zach.warecreate