Catapult auto roller not rolling a cl |
||||
Issue descriptionWe had a cl land in catapult ~3 hours ago, and the catapult auto roller still hasn't picked it up yet and has a status of "up to date." We turned the auto roller off for a little while yesterday while merging a feature branch. But the merged changes were rolled to chromium just fine, as was a follow-up roll for 3 other cls afterward last night. I also just toggled it from running to stopped and back again with no change. Commit in question: https://github.com/catapult-project/catapult/commit/9e84e9f4d0120e980c94b99fdaf287c729d0fe97 Last roll made: https://codereview.chromium.org/2170183003/
,
Jul 22 2016
Okay, the last roll was https://codereview.chromium.org/2170183003, which rolled to https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+/20358d6bf8c99ec34037b78e0f8b9022622d362a Looking at tip of master: https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+/master 20358d6 is the most recent commit there. The autoroller looks at the googlesource mirror, not GitHub, so as far as it's concerned it's up to date. My guess is that maybe the GitHub importer to googlesource has stopped working or is lagging behind?
,
Jul 22 2016
KI; b/30305746 The GitHub poller froze for several hours this morning, resulting in a loss of event activity. So quite a few repositories are behind.
,
Aug 5 2016
,
Aug 5 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by aiolos@chromium.org
, Jul 22 2016