UTAH

retry for bzr failures

Bug #1185584 reported by Paul Larson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UTAH
Fix Released
Medium
Andy Doan
UTAH 0.13

Bug Description

http://10.98.0.1:8080/job/saucy-server-amd64-smoke-raid1/30/artifact/log/utah-9426.syslog.log/*view*/ is a job I saw today that failed because of some bzr error. I see in runner.py where a specific type of of bzr failure is handled, but not others.
I think there are two things we should consider here:
1. better reporting of what caused us to fail out of there if it wasn't the specific thing we try to handle. Something more than "ERROR: Errors encountered during testing"
2. I think we should be more flexible on the bzr errors for which we retry.

Related branches

lp://qastaging/~doanac/utah/bzr-retry
Javier Collado (community): Approve
Andy Doan (community): Needs Resubmitting
Diff: 471 lines (+150/-124)
6 files modified
utah/client/common.py (+18/-0)
utah/client/runner.py (+34/-74)
utah/client/tests/test_testsuite.py (+6/-6)
utah/client/tests/test_vcs_bzr.py (+38/-31)
utah/client/testsuite.py (+5/-12)
utah/client/vcs.py (+49/-1)
Andy Doan (doanac)
Changed in utah:
assignee: nobody → Andy Doan (doanac)
importance: Undecided → Medium
milestone: none → 0.13
Revision history for this message
Andy Doan (doanac) wrote :

I did a lot of cleanup in this branch to lead to an actual easy-to-read solution. The key thing you'll want to look at is:

 http://bazaar.launchpad.net/~doanac/utah/bzr-retry/revision/928

Javier Collado (javier.collado)
Changed in utah:
status: New → In Progress
Andy Doan (doanac)
Changed in utah:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.