client.py failures should cause builds to be automatically respun

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
8 years ago
7 years ago

People

(Reporter: jhopkins, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
When client.py fails to check out sources, it is up to the user to resubmit their build.  Ideally, this should be automatically handled using the buildbot 'retry' logic.
for what its worth, we have an internal-to-client.py retry logic.

You can bump the retries via command-line arg to client.py. If this is about using the buildbot 'retry' logic, that might be harder especially coupled with the work gozer is headed toward.
This isn't about the internal retry logic. Sometimes client.py does fail, even trying a download twice (e.g. hmo error)

What we're looking at here is that if client.py fails, then the build should be automatically respun using the build exception (purple) mechanism.
Summary: client.py failures should be auto-retried → client.py failures should cause builds to be automatically respun
At the moment, the client.py process is embedded into the make process. Considering this, I don't think we can do too much about that at the moment, so I think whilst this is ideal, given the internal logic client.py has, this is wontfix for now.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.