Closed Bug 771375 Opened 12 years ago Closed 12 years ago

Should attempt to run tests multiple times when updating dashboard, rather than bailing out on failure

Categories

(Testing Graveyard :: Eideticker, defect)

Product:
Testing Graveyard
Component:
Eideticker
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: wlach, Unassigned)

Details

Right now we just halt the update dashboard script on failure. This used to make sense when our code was not robust and we wanted to make issues visible, unfortunately I think at this point I have fixed most of the low-hanging fruit and the remaining issues are due to the LG G2X that we're using for dashboard tests being flakey.

Since restarting the update dashboard script seems to resolve the issue, it seems like this is due to some kind of intermittent network issue or something. Let's get around this by just running tests again (up to 3 tries, say) instead of bailing out. This will hopefully ensure we get a good, representative sample of performance on a daily basis.
Fixed: https://github.com/mozilla/eideticker/commit/49f114fd6ab7f58bd7567f53697d93b19bdd7bbe
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.