Neal Norwitz schrieb: > The next releases of 2.6/3.0 are planned for April 2, just over a week > from now. There is much work that needs to be done. The buildbots > are in a pretty sad state and the gods are seeing too much red. > > http://www.python.org/dev/buildbot/stable/ > http://www.python.org/dev/buildbot/all/ > > See my other mail that discusses the stable buildbots. The criteria > for release is that all the stable buildbots are passing all the > tests. So we really gotta get these green before Barry notices. You > don't want to see Barry angry. You wouldn't like him when he's angry. > > I propose a code chill for new features. Changes to doc and tests can > continue as usual. However, only submit a new feature *after* you fix > a broken test first. If we have to get draconian, we can start > breaking fingers when you break a test just like we do at work. :-) > > Specifically tests that need some TLC are: > * test_winsound > - > http://www.python.org/dev/buildbot/stable/x86%20XP-3%20trunk/builds/1166/step-test/0
test_winsound on this buildbot only passes when I have an open remote desktop connection to the (virtual) machine. I have not found any other way to make these tests pass (I tried 'net stop beep', disabling the sound driver, removing the sound driver, disconnecting the hosts sound driver, and maybe other things). The only other thing hat I can image would be to disable the winsound tests... Thomas _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
