Closed
Bug 1247286
Opened 10 years ago
Closed 10 years ago
add retry logic to config_seta.py
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kmoir, Assigned: kmoir)
References
Details
Attachments
(1 file, 1 obsolete file)
|
1.94 KB,
patch
|
Callek
:
review+
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
in case seta server in intermittently unavailable
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → kmoir
| Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8717943 -
Flags: review?(bugspam.Callek)
| Assignee | ||
Updated•10 years ago
|
Attachment #8717943 -
Flags: review?(bugspam.Callek)
| Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8717943 -
Attachment is obsolete: true
| Assignee | ||
Updated•10 years ago
|
Attachment #8717960 -
Flags: review?(bugspam.Callek)
Comment 3•10 years ago
|
||
Comment on attachment 8717960 [details] [diff] [review]
bug247286.patch
Review of attachment 8717960 [details] [diff] [review]:
-----------------------------------------------------------------
::: mozilla-tests/config_seta.py
@@ +57,5 @@
> + if retries < 1:
> + raise Exception("Could not fetch url '%s'" % url)
> + retries -= 1
> + print("Retrying")
> + time.sleep(60)
I've never been a big fan of `while True` in code thats not meant to live forever. Too easy to accidentally break the assumptioned logic at some point.
That said, I'm not going to r- for it since this is relatively clean code and leave it up to you.
@@ +71,1 @@
> data = json.loads(response.read())
I'm more likely to have wanted the retry logic out here, due to possible cases of severed pipe/abnormal socket termination that merely causes invalid json and not the innability to read SETA. But either way this is an improvement I'm happy to take.
Attachment #8717960 -
Flags: review?(bugspam.Callek) → review+
| Assignee | ||
Updated•10 years ago
|
Attachment #8717960 -
Flags: checked-in+
| Assignee | ||
Comment 4•10 years ago
|
||
in production
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•