[x]
):I didn't know where to post this one, but I did update my gitea to 1.11-rc1 and since then my PRs get stucked in "Checking for merge conflicts, try again in a few moments" after merging in the main branch. I did roll back to 1.10.2 and it seems to work well on that one.
@Marcsiq2 rolling back to 1.10.2 doesn't necessary mean that there was a problem on 1.11 - depending on how you rolled back. The worklist could have just taken that long to work through.
We need some log information to work out what is going wrong - if anything.
There were three major changes to the PR checking:
That means that there's potentially lots more PR checking to do - although the queue is uniqued by PRID - possibly we're doing too much for example if the status check fails then the status will remain in checking.
We need logs. Log trace would have told us what the pull request tester was doing here.
For future reference this configuration should give us TRACE level logs for the pull service:
[log]
MODE=...,traceconsole ; Add the traceconsole logger to your current log modes
...
[log.traceconsole]
MODE=console
LEVEL=trace
EXPRESSION=services/pull
Thank you very much for your detailed help! I'll try that.
The console log is emitted on stdout. You can change the mode to file and set a FILE_NAME if you can't use the console.
On 1.10 the EXPRESSION should be models/pull
If you're getting the problem on 1.10 it is likely that you're facing the issue that there is just one worker running the pull request task and it's just busy.
Find there logs for both 1.10 and 1.11rc1
1.10 worked fine after a restart, while 1.11 is stuck in "checking merge conflict" and nothing else appears on the log.
And all this appears and the "checking..." disappears after restarting gitea.
I think I've found the cause.