Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd step to ensure Buildbot checks out right commit #531
Conversation
|
This is awesome! Thanks for doing this. I'm willing to give this a try - should really help! Just one issue: |
aneeshusa
force-pushed the
aneeshusa:check-that-actual-revision-matches-requested
branch
from
d5aafe4
to
6d76cc2
|
Fixed the nit. I haven't seen this happen too many times in the past (I'm hoping it didn't just silently happen!) so I'm not sure how helpful this is, but it does give me more peace of mind. |
|
|
We are using `retryFetch=True` to have Buildbot retry git fetches if they error out, as we often encounter intermittent errors (e.g. network problems). However, Buildbot will allow not only the first fetch + checkout to fail, but also the second (final) fetch + checkout to fail as well (which I consider a bug in Buildbot), making it possible for Buildbot to run a build on the wrong revision, causing confusion. Retrying failed fetches is too useful to disable. Hence, to work around this, add a custom step to all builds that checks if the commit we requested (the `revision` property) matches the actual commit Buildbot checks out, and fail the build if not the case.
aneeshusa
force-pushed the
aneeshusa:check-that-actual-revision-matches-requested
branch
from
6d76cc2
to
de46d64
|
@bors-servo r+ |
|
|
|
|
bors-servo
added a commit
that referenced
this pull request
Nov 1, 2016
…uested, r=larsbergstrom Add step to ensure Buildbot checks out right commit We are using `retryFetch=True` to have Buildbot retry git fetches if they error out, as we often encounter intermittent errors (e.g. network problems). However, Buildbot will allow not only the first fetch + checkout to fail, but also the second (final) fetch + checkout to fail as well (which I consider a bug in Buildbot), making it possible for Buildbot to run a build on the wrong revision, causing confusion. Retrying failed fetches is too useful to disable. Hence, to work around this, add a custom step to all builds that checks if the commit we requested (the `revision` property) matches the actual commit Buildbot checks out, and fail the build if not the case. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/531) <!-- Reviewable:end -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
aneeshusa commentedOct 30, 2016
•
edited by larsbergstrom
We are using
retryFetch=Trueto have Buildbot retry git fetches ifthey error out, as we often encounter intermittent errors (e.g. network
problems).
However, Buildbot will allow not only the first fetch + checkout to
fail, but also the second (final) fetch + checkout to fail as well
(which I consider a bug in Buildbot), making it possible for Buildbot
to run a build on the wrong revision, causing confusion.
Retrying failed fetches is too useful to disable.
Hence, to work around this, add a custom step to all builds that checks
if the commit we requested (the
revisionproperty) matches theactual commit Buildbot checks out, and fail the build if not the case.
This change is