Closed csymeonides-mf closed 3 years ago
Yes, I'm seeing this again too now :(
@csymeonides-mf are you using batch-mode?
The linear backoff change (https://github.com/smarkets/marge-bot/pull/265) was merged but it isn't part of release 0.9.4.
Until a new release is generated you could run the branch version... 😞
@sysadmiral oops my bad, I saw the date on the PR and assumed it was included in the release. Any idea when the next release will happen?
@snim2 we aren't using batch mode, would that help?
@csymeonides-mf I'm pretty sure that the linear back-off isn't in use in batch mode (I wrote the PR BTW), so I'd stick with what you've got TBH!
Will wait for the next release and try again.
Hey @csymeonides-mf , you could also try smarkets/marge-bot:master
image before the new release.
Yes, I'm seeing this again too now :(
@snim2 Do you mean your last PR may be insufficient to fix this issue?
@tclh123 I think we are running the latest release rather than master, but I will check for you later today...
@tclh123 yep, we have this in our marge-bot.service
:
ExecStartPre=/usr/bin/docker pull smarkets/marge-bot
and we restart with cron
every night.
Marge version 0.9.5 released, which contains @snim2 's fix. You could also use the latest
image tag.
Thank you! Will report back if the problem reoccurs.
Presumably the same issue as #263 (merge fails intermittently with "Branch cannot be merged" error, succeeds when assigning back to Marge)
Marge version: 0.9.4 We are running it in docker using the
stable
tag which is currentlysha256:5d5d9406d087d8119a2267d6561f22d7b5b090b75bf109817e3cbaaf8b8e7d71
Gitlab version: 13.5.2 (187cae1b32b)
Marge log:
Gitlab log:
Then when re-assigning to Marge:
And the Gitlab log: