DebugHooksServerSuite.TestRunHook signal: killed

Bug #1612747 reported by Curtis Hovey
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Christian Muirhead

Bug Description

As seen at

    c.Assert(err, jc.ErrorIsNil)
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc820216560), Stderr:[]uint8(nil)} ("signal: killed")

affects: juju-core → juju
Revision history for this message
Curtis Hovey (sinzui) wrote :

This fails on s390x more often than other arch and it has failed 4 times in one week. Given the good quality tests are in now, this test needs fixing.

Changed in juju:
milestone: none → 2.1.1
importance: Medium → High
tags: added: s390x
Revision history for this message
Christian Muirhead (2-xtian) wrote :

I can see the same failure if I add a delay to the goroutine the test starts - this would match the behaviour on a heavily loaded test machine. The flock command in the test has a 5s timeout, but the select loop further down has a 10s timeout, so I've increased the flock command to match.

Revision history for this message
Christian Muirhead (2-xtian) wrote :
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Christian Muirhead (2-xtian)
Changed in juju:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju:
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.