Merge lp:~mars/launchpad/use-zope.testing-3.9.4-p1 into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Māris Fogels on 2010-06-10 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 10991 |
| Proposed branch: | lp:~mars/launchpad/use-zope.testing-3.9.4-p1 |
| Merge into: | lp:launchpad |
| Diff against target: |
14 lines (+2/-2) 1 file modified
versions.cfg (+2/-2) |
| To merge this branch: | bzr merge lp:~mars/launchpad/use-zope.testing-3.9.4-p1 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Nelson (community) | code | 2010-06-10 | Approve on 2010-06-10 |
|
Review via email:
|
|||
Commit Message
Update to zope.testing-
Description of the Change
Hi,
This branch moves us onto a new post-release version of zope.testing-3.9.4. This fixes a problem where the testrunner would crash when printing doctest exceptions. The patch was backported from https:/
Test command: bin/ec2 test
Lint: none
Pre-implementation with: gary_poster
Maris
| Gary Poster (gary) wrote : | # |
This change is really no more or less likely to break 2.6 than a code change in LP itself--though I grant you, if this failed in 2.6 the failure might be more spectacular than usual. :-)
I think running some representative tests on a local developers' Lucid machine should be enough of a failsafe for now.
In terms of automated tests, at this instant we are trying to test 2.6 with the buildbot bzr builder. Not ideal, but something. EC2 changes will come later this cycle as it becomes more and more certain that we will be able to meet our goal of switching to Lucid in the DC this time around.

Thanks Maris.
Is it possible with this kind of change to have ec2 run the tests with both 2.5 and 2.6? Is that even necessary?