Closed Bug 1259325 Opened 9 years ago Closed 9 years ago

Improve retries for retrieving SETA config

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

References

Details

Attachments

(1 file)

We've been hitting socket.error exceptions when getting SETA data (see bug 1176784) but they're not getting caught by the retry logic we already have. This leaves the masters in a bad state where they consume jobs rapidly and fail on them, after raising exceptions.TypeError: unbound method __init__() must be called with C instance as first argument (got MockCommand instance instead) in buildbot's Build.setupBuild.
Does moves all the connection, reading, and decoding inside the try block with the retries. Adds handling for JSON decode exceptions too. If this is r+ could you get it landed too ?
Attachment #8734227 - Flags: review?(kmoir)
Attachment #8734227 - Flags: review?(kmoir) → review+
Comment on attachment 8734227 [details] [diff] [review] [buildbot-configs] Retry harder thanks Nick!
Attachment #8734227 - Flags: checked-in+
Landed at http://hg.mozilla.org/build/buildbot-configs/rev/3a24d5fe45b9 at Thu, 24 Mar 2016 09:39:31 -0400 (5 days ago), with merge to production.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: