Closed Bug 1187521 Opened 9 years ago Closed 8 years ago

"fail to push changes" occurred on 2 independent systems - logic error?

Categories

(Developer Services :: General, task)

Product:
Developer Services
Component:
General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: hwine, Unassigned)

References

Details

(Whiteboard: [vcs-sync]) 

Bug 1187212 was a user impacting problem to which a workaround was applied to unblock devs.

However, the circumstances and finding suggest there may be a deeper bug.

During this event, one project branch, 'larch' failed to update on github. This was while we were running modern vcs-sync in 2 different aws accounts (parallel operation prior to cutover). Both systems had identical conditions. As of this time, no log analysis has been done to correlate timing.

Both machines had:
 a) the hg repository properly up to date in staging/
 b) both the hg & git repositories up to date and coverted in conversion/
 c) either system was capable of updating github, but neither did
 d) both systems thought there was nothing to do for 'larch'

There hadn't been too much activity on larch, at the time of report, there were a batch of commits 4 & 5 days prior (merge) and one from 7 days prior. The latest commit showed on the various systems as follows:

    -4d     hg.mozilla.org/projects/larch   (hg)
    -4d     vcs-sync .../staging/larch      (hg) (both hosts)
    -4d     vcs-sync .../conversion/larch   (hg) (both hosts)
    -4d     vcs-sync .../conversion/larch   (git) (both hosts)
    -7d     github.com/mozilla/gecko-dev    (git)
Problem hasn't been seen in a year, assuming gone
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.