Launchpad itself

test suite run leaving stale rabbitmq processes

Bug #961032 reported by Tom Haddon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Critical
Unassigned

Bug Description

Just got an alert for number of processes on pilinut (the db-devel builder) and saw lots of stale rabbitmq processes: https://pastebin.canonical.com/62692/

Tom Haddon (mthaddon)
tags: added: canonical-losa-lp
Laura Czajkowski (czajkowski)
Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Robert Collins (lifeless) wrote :

Tentatively tagging paralleltest - this may explain some of the hangs seen so far.

tags: added: paralleltest
tags: added: build-infrastructure test-system
Revision history for this message
Gary Poster (gary) wrote :

Removing paralleltest: have not seen hangs, and rabbitmq should be killed when lxc containers are killed.

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

Well--this could be paralleltest in that the project should effectively fix this bug...

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 961032] Re: test suite run leaving stale rabbitmq processes

It won't fix it for non parallel runs, but IMO it would be fine to say
'everyone should run on lxc ephemeral everywhere' and be done with the
issue.

Curtis Hovey (sinzui)
tags: added: spurious-test-failure
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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