git checkout fails in scallywag

[Jon Turney]

On 09/09/2026 18:08, Brian Inglis via Cygwin-apps wrote:
> On 2026-09-09 08:24, Marco Atzeri via Cygwin-apps wrote:
>> On 09/09/2026 15:04, Andrew Schulman via Cygwin-apps wrote:
>>> In my latest push of fish to scallywag
>>> (https://github.com/cygwin/scallywag/actions/runs/34336457868/ 
>>> job/102416876538#annotation:26:16),
>>> the build fails in the source step. There's no build log that I can 
>>> see, but
>>> at the top of the page under Annotations, it says:
>>>
>>> Post Run action/checkout@v7
>>> The process 'D:\cygwin\bin\git.exe' failed with exit code 128
>>>
>>> Can you advise? Something I'm doing wrong?
> 
>> there are spurious random failures; I assume probably due to system load
>>
>> see id=12549 immediate failure and 12551 rerun log
> 
> Hi Andrew,
> 
> We all get them - check failed jobs:
> 
>      $ cygstart https://cygwin.com/cgi-bin2/jobs.cgi?status=build+failed
>      $ "$BROWSER" https://cygwin.com/cgi-bin2/jobs.cgi?status=build+failed
> 
> and look for short durations < 0:04:00, normally in source build, then 
> for your own jobs, you can just:
> 
>      $ ssh cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org jobs rerun JOBID
> 
> and it will resubmit the job for you under a new id.
> 
> I have also experienced transient GH Scallywag source package download 
> failures from GNU and mirrors (manuals and sources) and other bot- 
> protected sites.
> 
> Also remember you can only similarly deploy jobs where build succeeded 
> under cygwin-packages git master/main branches, not playground or other:
> 
>      $ ssh cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org jobs deploy JOBID
> 
> If you want to deploy from playground or other branch, or where some 
> tests failed, you have to continue using cygport ... upload.

Just to note that you can tell scallywag to skip running the package 
tests with "--push-option=notest" (for a single build) or by adding 
"SCALLYWAG=notest" to your cygport (permanently).

See [1].

[1] https://cygwin.com/packaging/build.html

> [I am writing this to remind myself and others who build packages 
> infrequently.]