Mir

Tests that use the InProcessServer bind the default socket file

Bug #1271604 reported by Alexandros Frantzis on 2014-01-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Alan Griffiths
mir (Ubuntu)
Medium
Unassigned

Bug Description

Tests that use the InProcessServer should use only in process communication pathways (socketpair etc), but end up opening and binding the default socket file anyway. This was found by accident when crashing a test that uses InProcessServer, leaving the default socket file in the file system and being unable to run the test again.

See line 505 in http://paste.ubuntu.com/6797795/

Related branches

Alexandros Frantzis (afrantzis) wrote :

To easily reproduce: touch /run/user/$(id -u)/mir_socket

Changed in mir:
assignee: nobody → Alan Griffiths (alan-griffiths)
Changed in mir:
status: New → Confirmed
Changed in mir:
milestone: none → 0.1.5
status: Confirmed → In Progress
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: In Progress → Fix Committed
Daniel van Vugt (vanvugt) wrote :

mir (0.1.4+14.04.20140204-0ubuntu1) trusty; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Fix Released
Changed in mir:
importance: Undecided → Medium
Changed in mir:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers