testtools 0.9.13 backwardiincompatible with 0.9.12

Bug #929063 reported by Tres Seaver on 2012-02-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subunit
Medium
Jonathan Lange
testtools
Critical
Jonathan Lange

Bug Description

The zope.testrunner.subunit tests *which rely on testtools) broke with
the release of 0.9.13. E.g.:

   http://buildbot.afpy.org/ztk1.1/builders/Python2.5.5%20Linux%2064bit/builds/147/steps/test%20ztk/logs/stdio

They passed the night before the release, with no changes between the
two runs in zope.testrunner.

Related branches

Jonathan Lange (jml) wrote :

Thanks Tres. Looks like subunit itself is relying on an internal API of testtools.

I'll restore the internal API, do another release of testtools and file a patch against subunit.

Changed in testtools:
status: New → Triaged
importance: Undecided → Critical
Changed in subunit:
status: New → Triaged
importance: Undecided → Medium
Jonathan Lange (jml) on 2012-02-09
Changed in testtools:
status: Triaged → In Progress
assignee: nobody → Jonathan Lange (jml)
Jonathan Lange (jml) on 2012-02-09
Changed in subunit:
status: Triaged → In Progress
assignee: nobody → Jonathan Lange (jml)
Jonathan Lange (jml) wrote :

OK. testtools trunk now works with the latest release of subunit and subunit itself has been updated to no longer use the private API. Will do a release of testtools.

Changed in testtools:
status: In Progress → Fix Committed
milestone: none → next
status: Fix Committed → Fix Released
Jonathan Lange (jml) on 2012-03-26
Changed in subunit:
status: In Progress → Fix Committed
Changed in subunit:
milestone: none → next
Changed in subunit:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers