Author ned.deily
Recipients ezio.melotti, ned.deily, python-dev, r.david.murray, terry.reedy, zach.ware
Date 2014-05-04.02:35:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399170935.03.0.392931364558.issue18604@psf.upfronthosting.co.za>
In-reply-to
Content
For some reason, the newly-added Tk instantiation check causes the OS X Cocoa Tk to segfault when tests are run under regrtest -jn option, which causes each test to be run under a separate subprocess called from a separate thread.  Somewhat surprisingly, the segfault doesn't seem to happen under the same conditions with 2.7, only with 3.4 and default, so there is something more at play here.  But with the imminent tagging of 3.4.1rc1, I think it is better to disable the check for 3.4 (and default) on OS X pending further investigation.  The check is redundant: if Tk doesn't work for some reason, the individual test should fail anyway, just a bit later.
History
Date User Action Args
2014-05-04 02:35:35ned.deilysetrecipients: + ned.deily, terry.reedy, ezio.melotti, r.david.murray, python-dev, zach.ware
2014-05-04 02:35:35ned.deilysetmessageid: <1399170935.03.0.392931364558.issue18604@psf.upfronthosting.co.za>
2014-05-04 02:35:34ned.deilylinkissue18604 messages
2014-05-04 02:35:34ned.deilycreate