fx-team branch of gecko-dev hasn't synced in 8 hours

RESOLVED FIXED

Status

Developer Services
Mercurial: hg.mozilla.org
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: coop, Unassigned)

Tracking

Details

(Whiteboard: [vcs][beagle])

(Reporter)

Description

3 years ago
Nick reported this in #releng:

[2:41pm] nalexander: coop|buildduty: https://github.com/mozilla/gecko-dev/tree/fx-team is not looking happy.  It's 7 hours behind.
[2:46pm] coop|buildduty: hwine, pmoore|back-later ^^
[2:47pm] coop|buildduty: i’m looking at https://wiki.mozilla.org/ReleaseEngineering/VCSSync/HowTo to try to resolve this
[2:48pm] hwine: coop|buildduty: so a) that repo is served by new, not legacy; b) double check commits - times can be confusing with dvcs
[2:52pm] coop|buildduty: hwine: checking mail, i haven’t received a beagle conversion mail since last night. is there a way to restart the process?
[2:53pm] hwine: iirc, you don't get mail when things are "ok" -- let me check mine
[2:54pm] hwine: (you only get "ok" when there's a prior problem)
[2:58pm] hwine: coop|buildduty: I don't see any obvious issues, but let me change the crontab - atm emails only going to pete
[3:01pm] hwine: coop|buildduty: changed crontab emails to come to all. Crontab runs every minute

Latest commit on github as of writing is:

https://github.com/mozilla/gecko-dev/commit/799366a5d93536324874f9e6ea8f66c29765fa7f
(Reporter)

Comment 1

3 years ago
hghooks moved repos recently: bug 1052201

Possible culprit?
Stuck rsync'ing log files:

[vcs2vcs@vcssync1.srv.releng.usw2.mozilla.com logs]$ ps -ef | grep rsync
vcs2vcs  23292 23238  0 06:55 ?        00:00:00 rsync -e ssh -oIdentityFile=~/.ssh/vcs-sync_rsa -azv . pmoore@people.mozilla.org:/home/pmoore/public_html/vcs2vcs/gecko-dev/
vcs2vcs  23293 23292  0 06:55 ?        00:00:00 ssh -oIdentityFile=~/.ssh/vcs-sync_rsa -l pmoore people.mozilla.org rsync --server -vlogDtprze.iLs . /home/pmoore/public_html/vcs2vcs/gecko-dev/
vcs2vcs  25509 25466  0 12:56 pts/3    00:00:00 grep rsync
The immediate issue is all resolved, and I'll create other bugs for the things to prevent recurrence.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Created bugs 1054048 and 1054050 for permanent solutions.
See Also: → bug 1054048, bug 1054050
(Assignee)

Updated

3 years ago
Product: Release Engineering → Developer Services
You need to log in before you can comment on or make changes to this bug.