Merge lp:~ricmm/ubuntu-app-launch/signal-start-on-started into lp:ubuntu-app-launch/13.10
Proposed by
Ricardo Mendoza
Status: | Merged |
---|---|
Approved by: | Gerry Boland |
Approved revision: | 78 |
Merged at revision: | 78 |
Proposed branch: | lp:~ricmm/ubuntu-app-launch/signal-start-on-started |
Merge into: | lp:ubuntu-app-launch/13.10 |
Diff against target: |
12 lines (+1/-1) 1 file modified
libupstart-app-launch/upstart-app-launch.c (+1/-1) |
To merge this branch: | bzr merge lp:~ricmm/ubuntu-app-launch/signal-start-on-started |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gerry Boland (community) | Approve | ||
Charles Kerr (community) | Approve | ||
PS Jenkins bot (community) | continuous-integration | Approve | |
Review via email: mp+190720@code.launchpad.net |
Commit message
Currently we are signalling observers that app started on the "starting" signal. This is racy, as the final exec might not have happened yet, so if a client tries to get the primary PID before the process has fully started, it might get one of the transitional PIDs of the scripts that run in between.
To post a comment you must log in.
PASSED: Continuous integration, rev:78 jenkins. qa.ubuntu. com/job/ upstart- app-launch- ci/141/ jenkins. qa.ubuntu. com/job/ upstart- app-launch- saucy-amd64- ci/143 jenkins. qa.ubuntu. com/job/ upstart- app-launch- saucy-armhf- ci/142 jenkins. qa.ubuntu. com/job/ upstart- app-launch- saucy-i386- ci/141
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild: 10.97.0. 26:8080/ job/upstart- app-launch- ci/141/ rebuild
http://