kumarUjjawal commented on issue #22455:
URL: https://github.com/apache/datafusion/issues/22455#issuecomment-4525783909

   Some of our ci jobs are failing regularly:
   
   - 
https://github.com/apache/datafusion/actions/runs/26333321641/job/77522875542
   - 
https://github.com/apache/datafusion/actions/runs/26334235111/job/77525452721?pr=22444
   - 
https://github.com/apache/datafusion/actions/runs/26329506986/job/77513261122
   
   I asked codex about it:
   
   ```
     the job  failed in actions/checkout, before Setup
     Rust toolchain or any Rust tests started. The errors are submodule fetch
     failures for parquet-testing and apache/arrow-testing: git exit 128, “did 
not
     contain <commit>”, “the remote end hung up unexpectedly”, and “could not 
read
     Username for https://github.com: terminal prompts disabled”. I sampled 
several
     other failed Rust workflow runs from May 23, 2026 across unrelated PRs and 
saw
     the same pattern in different jobs, including Linux and macOS. I also 
checked
     one rerun-success case where attempt 1 failed in checkout and attempt 2 
passed
     with no code change.
   
     Why this keeps happening: the Rust workflow uses actions/checkout@v6 with
     submodule checkout enabled in many jobs, and GitHub’s checkout docs say
     fetch-depth defaults to 1, submodules are fetched when that input is 
enabled,
     and the auth token is persisted in local git config by default. That means
     these jobs are doing shallow submodule fetches during checkout, which is
     exactly the phase that is flaking here. GitHub Status also shows recent 
GitHub
     Actions degradation incidents on May 20, 2026 and May 15, 2026, so
     platform-side instability is a plausible contributor. (github.com
     (https://github.com/actions/checkout/blob/main/README.md))
   
     My conclusion: the real issue is flaky submodule checkout against GitHub-
     hosted repos, not failing DataFusion tests and not a bad PR. The “could not
     read Username” message looks like a fallback symptom after the fetch 
breaks,
     not the main cause. The shared risk factors are actions/checkout, 
submodules:
     true, shallow fetch, and GitHub-side transport instability.
   ````


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to