Replying to myself - this looks more like a github issue: https://github.com/kamailio/kamailio/actions/runs/28104768963/job/83215913435?pr=4793
Run /home/runner/work/kamailio/kamailio/actions/.github/scripts/check-commit.sh fatal: unable to access 'https://github.com/kamailio/kamailio/': Failed to connect to github.com port 443 after 148341 ms: Couldn't connect to server Error: Process completed with exit code 128. Cheers, Henning From: Henning Westerholt via sr-dev <[email protected]> Sent: Mittwoch, 24. Juni 2026 16:21 To: [email protected] Cc: Henning Westerholt <[email protected]> Subject: [sr-dev] recently failing github checks Hello, I have noticed that recently a lot of automated github checks are failing, e.g. this one: https://github.com/kamailio/kamailio/actions/runs/28104768963/job/83215913571?pr=4793 Run /home/runner/work/kamailio/kamailio/actions/.github/scripts/check-cmake-format.sh >From https://github.com/kamailio/kamailio * branch master -> FETCH_HEAD * [new branch] master -> origin/master fatal: shallow file has changed since we read it Error: Process completed with exit code 128. I did some research and got some pointers about concurrent access issues on directories or a possible git bug. Is this something we need to fix from our side? https://github.com/python/cpython/issues/151365 If it's indeed a git regression, it should be fixed in a release next week according to the linked issue. Maybe somebody else knows more about it. Thanks, Henning
_______________________________________________ Kamailio - Development Mailing List -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
