Page MenuHomePhabricator

CheckUser CI failing due to failing to merge for all changes
Closed, ResolvedPublicBUG REPORT


Steps to replicate the issue (include links if applicable):

  • Submit any change to the CheckUser repo
  • Run CI

What happens?:
CI fails because Jenkins bot is unable to merge with the following error:

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.

What should have happened instead?:
CI should run

Other information (browser name/version, screenshots, etc.):
The last merged change was unable to merge the commit for only the coverage tests. However, the normal tests and gate-and-submit all passed as normal. Since the merge all new changes now fail tests, but the coverage tests now run without issue. This suggests to me that either it was the just merged change causing the issues. However, I have no idea why this issue is occurring as the change ( ) had no issues that I could see.

Event Timeline

Dreamy_Jazz triaged this task as Unbreak Now! priority.EditedDec 26 2022, 11:54 PM

UBN as blocking all CheckUser CI. Feel free to drop to High if not UBN-worthy.

Zabe has suggested this is T309376 and has asked for a restart of zuul.

Mentioned in SAL (#wikimedia-releng) [2022-12-27T00:48:24Z] <Reedy> restarted zuul using sudo /usr/sbin/service zuul restart for T325946

This is solved and the parent task can be used to work on a permanent solution.

Dreamy_Jazz claimed this task.
Dreamy_Jazz reassigned this task from Dreamy_Jazz to Reedy.