1964502 - "mach" commands are executing slowly due to invalid fetch settings for the "origin" remote following a VCS migration using Git Cinnabar

Status: RESOLVED WORKSFORME

(Developer Infrastructure :: Try, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Earlier today I used the steps at https://glandium.org/blog/?p=4370 to move from my plain git-cinnabar clone to the new git repository. Now when I'm trying to push to try via ./mach try fuzzy I can see the following behaviors:

1. When running the command for the first time the cache will be built up. So that's fine and the 2nd time the command is getting invoked should be fast, but that's not happening. It takes nearly a minute again before I can see the job selection panel.

2. When sending the request to try the submission never finishes. Maybe it's related to the warnings as shown in the log output.

Here the output when running the command:

mach try again                                                                                       git:(wdspec_android_crash_minidumpa↑1|…4
estimates: Runs 9 tasks (9 selected, 0 dependencies)
estimates: Total task duration 0:00:00
estimates: Should take about 0:00:00 (Finished around 2025-05-05 22:10)
Note: `--push-to-lando` is now the default behaviour of `mach try`.
Note: Use `--push-to-vcs` to push changes to try directly.
Auth0 token validated.
Using 4cc52826abd53e1121e4234d719cfd89ce58093 as the git base commit.
Submitting stack of 907107 nodes and the try commit.
warning: exhaustive rename detection was skipped due to too many files.
warning: you may want to set your diff.renameLimit variable to at least 34268 and retry the command.

Even after around 10 minutes I do not see any progress so I aborted the command.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

As it looks like other mach commands like mach wpt show this slowness as well. The same warning regarding rename detection is shown. So maybe it's not related to just the mach try command.

Glandium any idea what might have gone wrong when doing the conversion to git?

Comment 2

[Mike Hommey [:glandium]]

Submitting stack of 907107 nodes and the try commit.

It sounds like you are on a branch that is not based on the new repo.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

As mentioned I ran all the commands from the blog post but looking into the git config I was able to see the following settings for the main branch:

[branch "main"]
	remote = origin
	merge = refs/heads/bookmarks/central

This is clearly incorrect given that it should point to merge = refs/heads/main. The central bookmark is a relict from Mercurial.

But even updating this entry for main I still see those warnings and mach commands take ages. Is there something else that needs to get fixed?

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

There was actually another problem with the fetch settings of the remote origin. It listed fetch = +refs/heads/bookmarks/*:refs/remotes/origin/* which isn't valid anymore. Changing it to fetch = +refs/heads/*:refs/remotes/origin/* and running git remote update && git fetch made it work. Now everything runs again as fast as before.