Merge ~kissiel/plainbox-provider-checkbox:respawn-after-pmtest-reboots into plainbox-provider-checkbox:master
Proposed by
Maciej Kisielewski
Status: | Merged |
---|---|
Approved by: | Sylvain Pineau |
Approved revision: | b09f11afcda05bb3cab5a6fac2aab6f9e59fc369 |
Merged at revision: | 8ad9b4b3a77273bc4c6cffee609ee7f205667f28 |
Proposed branch: | ~kissiel/plainbox-provider-checkbox:respawn-after-pmtest-reboots |
Merge into: | plainbox-provider-checkbox:master |
Diff against target: |
51 lines (+7/-6) 2 files modified
bin/pm_test (+1/-1) jobs/stress.txt.in (+6/-5) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sylvain Pineau (community) | Approve | ||
Maciej Kisielewski | Needs Resubmitting | ||
Review via email: mp+328654@code.launchpad.net |
Description of the change
make pm_test-related jobs respawn checkbox after the reboot cycles
To post a comment you must log in.
To test it make sure you're have latest masters of [plainbox, checkbox-ng, plainbox- provider- checkbox] installed (globally, i.e. system-wide).
To do that, enter respective project's directory, and run:
./setup.py build && sudo ./setup.py install
Virtual env won't cut it, as after the reboot restart strategy will use the same 'binary' to run.
In theory re-establishing virtualenv is possible, but I haven't tried that and it seems not worth the hustle ATM.
I recommend doing that on a 'throwaway' installation (Though VM is not suitable as it's difficult - if not impossible - to run S3/S4 inside them)