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.
** Summary changed:
- intermitent test failure
+ upstart works as expected, notify-dbus-address tests fail depending on
system-wide session jobs
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315767
Title:
upstart works as expected, notify-dbus-address tests fail depending on
system-wide session jobs
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1315767/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
