bzr fails to build on vivid (release) and trusty (test-rebuild only)
Bug #1451448 reported by
Matthias Klose
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Vincent Ladeuil | ||
bzr (Debian) |
Fix Released
|
Unknown
|
|||
bzr (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned | ||
Vivid |
Won't Fix
|
High
|
Unassigned |
Bug Description
bzr fails to build on vivid (release) and trusty (test-rebuild only)
various test failures seen, likely exposed by python 2.7.10.
release:
https:/
test rebuild:
https:/
how to validate: successful build. the testsuite is run during the build
Related branches
lp:~vila/bzr/1451448-skip-racy-tests
- Richard Wilbur: Approve
-
Diff: 137 lines (+35/-7)5 files modifiedbzrlib/tests/test_http.py (+18/-3)
bzrlib/tests/test_osutils.py (+3/-1)
bzrlib/tests/test_transport.py (+2/-1)
bzrlib/tests/test_urlutils.py (+3/-2)
doc/en/release-notes/bzr-2.7.txt (+9/-0)
Changed in bzr (Ubuntu Trusty): | |
importance: | Undecided → High |
milestone: | none → trusty-updates |
status: | New → Confirmed |
Changed in bzr (Ubuntu): | |
milestone: | vivid-updates → ubuntu-15.10 |
Changed in bzr: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in bzr (Debian): | |
status: | Unknown → Confirmed |
Changed in bzr (Debian): | |
status: | Confirmed → Fix Released |
tags: |
added: verification-failed removed: verification-needed |
Changed in bzr (Ubuntu Trusty): | |
status: | Fix Committed → Confirmed |
Changed in bzr (Ubuntu Trusty): | |
status: | Confirmed → Fix Committed |
tags: | added: ftbfs |
Changed in bzr: | |
assignee: | nobody → Vincent Ladeuil (vila) |
status: | Confirmed → In Progress |
milestone: | none → 2.7b1 |
Changed in python2.7 (Ubuntu): | |
status: | New → Invalid |
Changed in python2.7 (Ubuntu Vivid): | |
status: | New → Invalid |
Changed in python2.7 (Ubuntu): | |
importance: | Undecided → High |
Changed in python2.7 (Ubuntu Trusty): | |
importance: | Undecided → High |
Changed in python2.7 (Ubuntu Vivid): | |
importance: | Undecided → High |
Changed in bzr: | |
status: | In Progress → Fix Released |
no longer affects: | python2.7 (Ubuntu Vivid) |
no longer affects: | python2.7 (Ubuntu Trusty) |
no longer affects: | python2.7 (Ubuntu) |
Changed in bzr (Ubuntu Vivid): | |
status: | New → Won't Fix |
To post a comment you must log in.
Sorry for the reply delay :-/
I've been able to reproduce on vivid.
These tests are racy (yet another occurrence of running a TCP server and client in the same process (different threads)).
Out of the ~800 http tests, those two ones are the simplest: they connect to an http server that always reply with a 'Bad status' message and close the connection.
Running 'bzr selftest --parallel=fork -v -s bt.test_ http.TestBadSta tusServer' repeatedly, I can:
- see the test pass,
- see the test fail as reported,
- see the test hang
Definitely a race :-/
This can be fixed in two ways:
- run the server in a separate process,
- identify the race more precisely and fix it.
The former requires some tedious work, the later requires some deep investigation :-/
I've sent a patch to debian to disable these tests until they are properly fixed. We don't lose significant coverage doing so (pqm will still run them to gate lp:bzr).