Forced analysis doesn't rerun the try-job |
|||
Issue descriptionhttps://11957-ac53c9e-dot-findit-for-me.appspot.com/waterfall/failure?redirect=1&url=https://luci-milo.appspot.com/buildbot/chromium.chromiumos/Linux%20ChromiumOS%20Builder%20%28dbg%29/92259 The analysis was forced to rerun on 09-30, but the try-job pointed to by the try-job link on the UI was on 09-24 while it is expected to run on 09-30 instead. https://screenshot.googleplex.com/2C0370Ex6eT.png
,
Oct 10 2017
,
Oct 10 2017
A rerun of https://12148-9334646-dot-waterfall-frontend-dot-findit-for-me.appspot.com/waterfall/build-failure?url=https://luci-milo.appspot.com/buildbot/chromium/Win/59636&debug=1 has triggered a new try job to run. Not sure if this bug still needs action.
,
Oct 10 2017
if so, you may close it after double checking with Brandon.
,
Oct 10 2017
So the build 92259 is not first build, that's why rerun the analysis will not rerun try jobs.
,
Oct 10 2017
Can you update the release process regarding this so that later we won't run into that again.
,
Oct 10 2017
Sure. I'll upload a change later today.
,
Oct 11 2017
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/339c9c82d7f1dabd314755e339844edaa00f76b6 commit 339c9c82d7f1dabd314755e339844edaa00f76b6 Author: Chan <chanli@chromium.org> Date: Wed Oct 11 17:15:19 2017 [Findit] Add a reminder to rerun first waterfall failure. When force a rerun of build failures to check if a release is success, we need to rerun a first failure so that a new try job can be triggered. Add a reminder in makefile. Bug: 770929 Change-Id: Ifee8e4341f6f511bfc60060ad1a0a9dc0111c459 Reviewed-on: https://chromium-review.googlesource.com/710834 Reviewed-by: Jeffrey Li <lijeffrey@chromium.org> Reviewed-by: Shuotao Gao <stgao@chromium.org> Commit-Queue: Chan Li <chanli@chromium.org> [modify] https://crrev.com/339c9c82d7f1dabd314755e339844edaa00f76b6/appengine/findit/makefile |
|||
►
Sign in to add a comment |
|||
Comment 1 by st...@chromium.org
, Oct 2 2017