Include more details when logging GitLabRebaseResultMismatch #336
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
perlun
commented
Jan 26, 2022
|
Ping @snim2. Any chance someone could review this within the near future? |
I've left you a comment, but I don't have rights to merge anything in this repo BTW! |
perlun
force-pushed
the
fix/log-rebase-result-mismatch-errors
branch
from
16e332e
to
34286d5
Compare
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.
We are seeing this locally for whatever reason, even though we are merging with margebot (e.g. multiple MRs in the same repo), and also in general whenever a branch is not up-to-date (=rebased on
masterin the main fork) when the MR gets assigned to the Marge-bot user. The aim here is to help to make debugging issues like this easier.marge-bot_1 | 2022-01-26 07:44:00,676 INFO Gitlab rebase didn't give expected result