Closed Bug 1270933 Opened 9 years ago Closed 7 years ago

mozilla-taskcluster does not deal well with "reset" repositories

Categories

(Taskcluster :: Services, defect)

Product:
Taskcluster
Component:
Services
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: dustin, Unassigned, Mentored)

Details

Joel noted that many of the twigs are not getting TC jobs triggered in bug 1252471 comment 21. Greg discovered that this is due to the pushid's on those repos being *less* than the recorded last pushid in mozilla-taskcluster's database. This occurred when those repositories were "reset", which is not uncommon in twig repositories. I'm not sure what the best fix would be -- perhaps on every poll, if the repo's pushid is less than the latest pushid, then reset the latest pushid backward to that value, or maybe even back to zero.
Component: Integration → Platform and Services
We'll be getting rid of mozilla-taskcluster, so this is not worth solving.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Component: Platform and Services → Services
You need to log in before you can comment on or make changes to this bug.