phase1: workaround gitverify 1st build failures on fresh workers #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently every 1st build on ephemeral build worker results in the failure of the `gitverify` build step as the stock buildbot Git() build step for some reasons just clones the Git repository into detached HEAD state. On the 2nd build using the same build worker Git() checkouts the branch and thus makes `gitverify` step happy and the builds then continues normally. This needs to be fixed properly, either by adjusting the `gitverify` check or adding suitable `mode` into Git() build step, but this needs more time and testing. So for now, lets simply workaround that issue by running Git() step two times. References: #5 Signed-off-by: Petr Štetiar <ynezz@true.cz>
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently every 1st build on ephemeral build worker results in the failure of the
gitverifybuild step as the stock buildbot Git() build step for some reasons just clones the Git repository into detached HEAD state.On the 2nd build using the same build worker Git() checkouts the branch and thus makes
gitverifystep happy and the builds then continues normally.This needs to be fixed properly, either by adjusting the
gitverifycheck or adding suitablemodeinto Git() build step, but this needs more time and testing.So for now, lets simply workaround that issue by running Git() step two times.
References: #5