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 paul.moore, steve.dower, tim.golden, zach.ware
Date 2016-08-12.17:12:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471021956.0.0.678344945934.issue27748@psf.upfronthosting.co.za>
In-reply-to
Content
test_winsound is rather annoying.  It currently attempts to determine whether a sound card is present, and whether particular system sounds are available.  These checks are fragile at best, and I routinely see failures that shouldn't be.  In particular, if I have an open RDP session to my ware-win81-release buildbot, test_winsound fails because it thinks the sounds should fail to play, but instead they succeed.

Rather than attempt to make the checks more robust, I suggest that we instead rip out the checks and simply ensure that each call that might succeed either returns normally or raises RuntimeError.  After all, we can't actually test whether a sound really played or not.
History
Date User Action Args
2016-08-12 17:12:36zach.waresetrecipients: + zach.ware, paul.moore, tim.golden, steve.dower
2016-08-12 17:12:36zach.waresetmessageid: <1471021956.0.0.678344945934.issue27748@psf.upfronthosting.co.za>
2016-08-12 17:12:35zach.warelinkissue27748 messages
2016-08-12 17:12:35zach.warecreate