buildd-slave.txt has a timing issue

Bug #553259 reported by Michael Nelson
6
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://code.edge.launchpad.net/~jml/launchpad/sftp-poppy/+merge/21627

and since then the buildd-slave.txt doctest fails intermittently like this:

https://lpbuildbot.canonical.com/builders/db_lp/builds/651/steps/shell_7/logs/summary

I can reproduce the issue locally if I manually ensure that the tachandler dies *after* the s.info() call is initiated.

Related branches

Revision history for this message
Michael Nelson (michael.nelson) wrote :

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

Changed in soyuz:
status: Confirmed → Triaged
tags: added: tech-debt
Changed in soyuz:
milestone: 10.04 → none
Revision history for this message
Michael Nelson (michael.nelson) wrote :

r9230 db-devel

Changed in soyuz:
assignee: nobody → Michael Nelson (michael.nelson)
milestone: none → 10.04
status: Triaged → Fix Committed
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
tags: added: qa-needstesting
tags: added: qa-untestable
removed: qa-needstesting
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.