upstart works as expected, notify-dbus-address tests fail depending on system-wide session jobs
Bug #1315767 reported by
Dimitri John Ledkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Fix Committed
|
Undecided
|
Unassigned | ||
upstart (Ubuntu) |
Fix Released
|
Undecided
|
Dimitri John Ledkov |
Bug Description
not ok 204 - ensure Session Init connects to D-Bus session bus when notified
wrong string value, expected 'init (upstart [0-9.][0-9.]*' got 'initctl: Name "com.ubuntu.
at tests/test_
/bin/bash: line 5: 6113 Aborted ${dir}$tst
FAIL: test_initctl
I've seen this failure on amd64, arm64 and powerpc. Retries did eventually pass the test-suite on amd64 & powerpc. However arm64 still fails on the official distro builders.
Related branches
lp:~xnox/upstart/do-not-launch-session-dbus
- James Hunt: Approve
-
Diff: 24 lines (+5/-2)1 file modifiedutil/tests/test_initctl.c (+5/-2)
Changed in upstart (Ubuntu): | |
assignee: | nobody → James Hunt (jamesodhunt) |
Changed in upstart (Ubuntu): | |
assignee: | James Hunt (jamesodhunt) → Dimitri John Ledkov (xnox) |
Changed in upstart: | |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
After starting upstart i've asserted that no jobs are running, however there there a few of them running, including user session dbus job that did notify upstart of its dbus address. Later in the test when we tried to notify our test upstart with test dbus address, test upstart would not connect to test dbus since it only accept dbus connections once and was already running on the other dbus.
This is racy & dependant on the jobs configured in /usr/share/ upstart/ session/
I've resolved this using "--no-startup- event" option. But it is inherently racy, as potentially all user-session test upstart spawns are affected. Thus something generic should be implemented in the test_common_ utilities, such that when test-upstart in user session mode is spawned global jobs are not executed.