Could not kill stale process /var/tmp/fatsam.test/librarian.pid.

Bug #671335 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I often get this kind of error when running the test suite:

Could not kill stale process /var/tmp/fatsam.test/librarian.pid

See fuller summary here: http://paste.ubuntu.com/526193/

I tried interrupting the test when this happened and running the whole thing again, but I guess that left another (or the same) pidfile in limbo and the problem repeated itself. It went away when I let the failed suite run to completion and _then_ ran it again.

Revision history for this message
Gary Poster (gary) wrote :

I don't see this myself, FWIW.

Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

I see it very frequently, several times in the average day of development. It costs me considerable time and energy, since interrupting the broken (and so generally pointless) ongoing test run seems to make the error come back next time.

Perhaps I'm hitting this because I do a lot of my work in a feature branch and so I'm switching back and forth between different schema versions, code versions, and sourcecode setups.

Revision history for this message
Gary Poster (gary) wrote :

See also bug 682861

Revision history for this message
Данило Шеган (danilo) wrote :

We've just had this on buildbot as well: https://lpbuildbot.canonical.com/builders/lucid_db_lp/builds/500/steps/shell_6/logs/summary

This requires LOSA action to clean-up, which is pretty bad IMHO. Could we not just try to clean-up .pid files for processes which don't exist at the start of 'make check' (or whatever happens on the buildbot)?

Also, if we start seeing it a bit more, we should probably raise the priority.

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.