Doug Hellmann <d...@doughellmann.com> 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. > > The latest word from Canonical is that they plan to package Python 3.4.3, due > to be released in about a month. It will take some additional time to put it > through their release process, and so there’s some uncertainty about how long > we would be without 3.x gate jobs, but it doesn’t look like it will be > indefinitely. > > To mitigate that risk, fungi has suggested starting to work on Debian Jessie > worker images, which would include a version of Python 3.4 that doesn’t have > the segfault issue. His goal is to have something working by around the end > of March. That gives Canonical up to a month to release the 3.4.3 package > before we would definitely move those tests to Debian. Whether we move any of > the other projects, or would move anyway if fungi gets Debian working more > quickly than he expects, would remain to be seen. > > Although we do have some risk of introducing Python 3 regressions into the > two libraries, I am inclined to go along with the infra team’s request and > disable the tests for a short period of time. The rootwrap library doesn’t > see a lot of changes, and we can rely on the messaging lib devs to run tests > locally for a little while. > > Before I give the go-ahead, I want to hear concerns from the rest of the > team. Let’s try to have an answer by the 29th (Thursday). I’m not involved with those two subprojects but as an Oslo member I’d +1 disabling python3.x for now. __________________________________________________________________________ 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
