Closed Bug 1173855 Opened 10 years ago Closed 10 years ago

Autophone - check for timeout in PerfTest.publish_results should test for timeout message

Categories

(Testing Graveyard :: Autophone, defect)

defect
Not set
normal

Tracking

(firefox41 affected)

RESOLVED FIXED
Tracking Status
firefox41 --- affected

People

(Reporter: bc, Assigned: bc)

References

Details

Attachments

(2 files)

Example email shows the timeout does not retry but fails after the first timeout. There was an error attempting to send test results to the result server http://phonedash.mozilla.org. Job https://treeherder.mozilla.org/#/jobs?filter-searchStr=autophone&exclusion_profile=false&repo=mozilla-inbound&revision=321a1148b604 Test autophone-s1s2 Phone nexus-s-2 Repository mozilla-inbound Build 20150610221245 Revision http://hg.mozilla.org/integration/mozilla-inbound/rev/321a1148b604 Exception <urlopen error [Errno 60] Operation timed out> Result { "blddate": 1433999565, "bldtype": "opt", "cached": false, "machineid": "Nexus S", "osver": "2.3.6", "phoneid": "nexus-s-2", "productname": "org.mozilla.fennec", "productversion": "41.0a1", "rejected": false, "revision": "http://hg.mozilla.org/integration/mozilla-inbound/rev/321a1148b604", "starttime": 148.0, "testname": "local-blank", "throbberstart": 1355.0, "throbberstop": 5418.0 } https://github.com/bclary/autophone/blob/master/tests/perftest.py#L188 uses a check for errno == 60 to determine if the urlopen failed due to a timeout. This is incorrect as the urllib2.URLError doesn't have a meaningful errno. A better check is to test if a string is found in the exception, e.g. 'timed out' in e
>>> import urllib2 >>> e = urllib2.URLError('timed out') >>> 'timed out' in e True >>> 'yoda' in e False
Attachment #8621118 - Flags: review?(gbrown)
Attachment #8621118 - Flags: review?(gbrown) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
This didn't work.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Just treat all exceptions the same. I've been testing this in production this morning and it appears to work fine.
Attachment #8621727 - Flags: review?(gbrown)
Blocks: 1174271
Comment on attachment 8621727 [details] [diff] [review] bug-1173855-followup.patch Review of attachment 8621727 [details] [diff] [review]: ----------------------------------------------------------------- That's certainly simpler and less hacky. Do you know why the "timed out" check was not working?
Attachment #8621727 - Flags: review?(gbrown) → review+
Nope. :-(
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: