buildd-slave.txt has a timing issue
Bug #553259 reported by
Michael Nelson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Michael Nelson |
Bug Description
We are not 100% sure that it is related, but a few weeks ago there were changes made to how processes are killed in tachandler:
https:/
and since then the buildd-slave.txt doctest fails intermittently like this:
https:/
I can reproduce the issue locally if I manually ensure that the tachandler dies *after* the s.info() call is initiated.
Related branches
lp:~michael.nelson/launchpad/db-enable-buildd-slavescanner.txt
- Björn Tillenius (community): Approve (release-critical)
- Abel Deuring (community): Approve (code)
-
Diff: 91 lines (+15/-37)3 files modifiedlib/lp/soyuz/doc/buildd-slave.txt (+1/-1)
lib/lp/soyuz/doc/buildd-slavescanner.txt (+2/-19)
lib/lp/soyuz/tests/test_doc.py (+12/-17)
Changed in soyuz: | |
status: | Confirmed → Triaged |
tags: | added: tech-debt |
Changed in soyuz: | |
milestone: | 10.04 → none |
tags: |
added: qa-untestable removed: qa-needstesting |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note: we tried to fix this once before, but it obviously didn't solve the core issue:
https:/ /code.edge. launchpad. net/~michael. nelson/ launchpad/ fix-buildd- slave-test/ +merge/ 21847