Re: [PATCH v3 09/10] fetch: fetch unpopulated, changed submodules

From: Glen Choo <chooglen@google.com>
Date: Mar 2, 2022, 23:25 UTC
Message-ID: <kl6lfso0djj8.fsf@chooglen-macbookpro.roam.corp.google.com>
In-Reply-To: <xmqq35k1pg4c.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 29 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>> Hi,
>>
>> On Sat, 26 Feb 2022, Junio C Hamano wrote:
>>
>>> A few tests added by this patch have been failing on one specific
>>> job (linux-gcc ubuntu-latest) at GitHub CI.
>>>
>>> https://github.com/git/git/runs/5341052811?check_suite_focus=true#step:5:3968
>>> https://github.com/git/git/runs/5343133021?check_suite_focus=true#step:4:5520
>>>
>>>     Side note: you may need to be logged in to GitHub to view them.
>>>     These two use different versions of CI to show the test traces;
>>>     in the latter you may have to click on right-facing rectangle on
>>>     the line with label "5520" to see the breakage.
>>>
>>> I think there is some baked-in assumption in the failing test what
>>> the name of the initial branch by default is, which may be the reason
>>> why this particular job fails while others don't.
>>>
>>> Can you take a look at it?
>>
>> The log says this:
>> ...
>> At least that's how _I_ tried to address similar issues in the test suite
>> in the past.
>
> Yes, I had a squashable fix/workaround queued since last night.

Thanks, both! I especially appreciate the pointers because I couldn't remember how to set the default branch off the top of my head.