Merge lp:~nuclearbob/utah/bug1082171 into lp:utah
Proposed by
Max Brustkern
Status: | Rejected |
---|---|
Rejected by: | Max Brustkern |
Proposed branch: | lp:~nuclearbob/utah/bug1082171 |
Merge into: | lp:utah |
Diff against target: |
47 lines (+14/-4) 1 file modified
utah/provisioning/vm/vm.py (+14/-4) |
To merge this branch: | bzr merge lp:~nuclearbob/utah/bug1082171 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Max Brustkern (community) | Disapprove | ||
Javier Collado (community) | Needs Fixing | ||
Review via email:
|
Description of the change
I've been unable to recreate the issue in lp:1082171 outside of the lab so far. This is the code I've been using to test it. Since it's just some additional logging, I'd like to consider merging it into the dev branch so we can see the output on all the normal smoke test jobs that are running.
To post a comment you must log in.
Unmerged revisions
- 794. By Max Brustkern
-
Writing log file size periodically to debug
Please find below some comments:
- Looks like the newly imported `time` module isn't being used anywhere.
- The `pass` statement in line 37 (438 in the source file) should be removed.
Isn't really part of this merge, but this line caught my eye:
while vm.isActive() is not 0:
- What is the set of valid output values of vm.isActive? Could "is not 0" be
dropped?
- How long does it take vm.isActive to return a value? Could that cause that
lots of log lines are printed to stderr?
Regarding the intended usage of this code. My understanding is that it will be
removed once the bug is fixed, so isn't something that we want to have in final
code. In such a case, while you're troubleshooting the problem, I think it
would be better to temporarily disable the jobs that update the packages in the
testing hardware and manually modify the installed .py files there. What do you
think about this?