On Tue, Jan 27 2015, Doug Hellmann wrote: > The infra team has been working hard to update our Python 3 testing for all > projects to run on 3.4 instead of 3.3. Two of the last projects to be able to > shift are oslo.messaging and oslo.rootwrap. The test suites for both projects > trigger a segfault bug in the 3.4 interpreter as it is shipped on Ubuntu > Trusty. The fix for the segfault is already available upstream, and the team > at > Canonical is working on packaging a new release, but our schedules are out of > sync. Maintaining a separate image and pool of testing nodes for 3.3 testing > of > just these two projects is going to be a bit of a burden, and so the infra > team > has asked if we’re willing to turn off the 3.3 jobs for the two projects, > leaving us without 3.x testing in the gate until the 3.4 interpreter on Trusty > is updated.
Isn't there any way to have an ugly work-around in those libs that wouldn't trigger the Python 3.4 segfault or at least disable the responsible tests until Python 3.4 gets fixed? -- Julien Danjou # Free Software hacker # http://julien.danjou.info
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
