Merge lp:~mterry/ubuntu-system-settings/crashed-socket into lp:ubuntu-system-settings
Status: | Merged |
---|---|
Approved by: | Ken VanDine |
Approved revision: | 1062 |
Merged at revision: | 1079 |
Proposed branch: | lp:~mterry/ubuntu-system-settings/crashed-socket |
Merge into: | lp:ubuntu-system-settings |
Diff against target: |
100 lines (+36/-26) 2 files modified
wizard/ubuntu-system-settings-wizard-cleanup.conf (+4/-25) wizard/ubuntu-system-settings-wizard.conf (+32/-1) |
To merge this branch: | bzr merge lp:~mterry/ubuntu-system-settings/crashed-socket |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ken VanDine | Approve | ||
Sebastien Bacher (community) | Approve | ||
PS Jenkins bot | continuous-integration | Needs Fixing | |
Review via email: mp+235352@code.launchpad.net |
Commit message
Prevent a crash in unity8 when the wizard also crashes or stops early. (LP: #1355892)
Move some of the socket cleanup from the 'cleanup' wizard job to the main job, while also avoiding the race that would create by stopping and starting unity8's job more carefully.
Description of the change
Prevent a crash in unity8 when the wizard also crashes or stops early. (LP: #1355892)
Move some of the socket cleanup from the 'cleanup' wizard job to the main job, while also avoiding the race that would create by stopping and starting unity8's job more carefully.
== Checklist ==
* Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes)
Yes
* Did you build your software in a clean sbuild/pbuilder chroot or ppa?
NA, just upstart changes
* Did you build your software in a clean sbuild/pbuilder armhf chroot or ppa?
NA, just upstart changes
* Has your component "TestPlan” been executed successfully on emulator, N4?
Yes
* Has a 5 minute exploratory testing run been executed on N4?
Yes
* If you changed the packaging (debian), did you subscribe a core-dev to this MP?
NA
* If you changed the UI, did you subscribe the design-reviewers to this MP?
NA
* What components might get impacted by your changes?
Just wizard
* Have you requested review by the teams of these owning components?
Yeah
FAILED: Continuous integration, rev:1062 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- ci/1520/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- utopic- touch/5071/ console jenkins. qa.ubuntu. com/job/ generic- mediumtests- utopic/ 3701 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- utopic- i386-ci/ 712 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- mako/4819/ console jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- utopic- armhf/6323 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- utopic- armhf/6323/ artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 13561 jenkins. qa.ubuntu. com/job/ autopilot- testrunner- otto-utopic/ 3093 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- utopic- amd64/4010 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- utopic- amd64/4010/ artifact/ work/output/ *zip*/output. zip
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/ubuntu- system- settings- ci/1520/ rebuild
http://