Autopilot tests are failing because Mir is refusing the connection

Bug #1520604 reported by Jonas G. Drange
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
Undecided
Michał Sawicz
unity8 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Reproduce:
Not sure

What happens:
After some time, autopilot tests start to fail even though the projects and branches are different. See [1], [2] and [3].

They fail with “UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is
running, and the correct socket is being used and is accessible. The shell may have
rejected the incoming connection, so check its log file”

[1] https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-touch/4291/
[2] https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-touch/4243/
[3] https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-vivid-touch/5409/

Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

Michael saw this unity crash file after seeing a symptom similar to the description.

Changed in canonical-devices-system-image:
assignee: nobody → Michał Sawicz (saviq)
status: New → Confirmed
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.