Issue metadata
Sign in to add a comment
|
Infra tryjobs bot_update doesn't apply DEPS patches before running gclient sync |
||||||||||||||||||||||||
Issue descriptionWhat steps will reproduce the problem? (1) Upload a DEPS roll to infra.git (like https://chromium-review.googlesource.com/c/372078/1) (2) Run the tryjobs (like https://luci-milo.appspot.com/swarming/task/30b7b34141fd0a10) (3) Look at the gclient json (like https://luci-milo.appspot.com/swarming/task/30b7b34141fd0a10/steps/bot_update/0/logs/json.output/0) What is the expected output? The hash for the rolled repository should be the post-roll value. (In this case, 86e917c99f25e9b421716d599ceeb5282e5de583) What do you see instead? The hash for the rolled repository hasn't changed. (In this case, it is still cca3a7f6fe042a3f745d40176b567a6bea75c6a1)
,
Aug 18 2016
Nope, Pawel patch was reverted, and this itself is KI, i'll find a dup.
,
Aug 18 2016
Putting this in the right component and at Pri-1 because this needs to be fixed before we land any more rolls in infra.git.
,
Aug 18 2016
,
Aug 18 2016
Yeah it is. I'll merge this into that, and update the summary and priority of that bug. This can't be a leave it for two months and then say "oh I wasn't making much progress and this seems tangled" issue, this is a launch blocker. I'm not sure what's so hard about if gerrit: check out ref gclient sync as opposed to if gerrit: check out ref gclient runhooks |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by hinoka@chromium.org
, Aug 18 2016Owner: phajdan.jr@chromium.org