Hi, On Wed, 23 Nov 2022, Jiang Xin wrote: > From: Jiang Xin <zhiyou.jx@xxxxxxxxxxxxxxx> > > Today I found lots of CI errors of my private host git repository > on GitHub. It is because the runner image "ubuntu-latest" of the > CI jobs is ubuntu 22.04 (jammy) instead of ubuntu 20.04 (focal). Excellent timing! This is indeed what I, too, ran into when adjusting microsoft/git to v2.39.0-rc0. Here are the relevant links for the failing and the succeeding runs, for the very same commit, but in different repositories and with different `ubuntu-*` images: Failing (ubuntu-22.04): https://github.com/dscho/git/actions/runs/3533530319/jobs/5939252441#step:1:8 Succeeding (ubuntu-20.04): https://github.com/microsoft/git/actions/runs/3532815597/jobs/5927646267#step:1:9 Having said that, I applied your fixes on top and pushed out a test branch, but `p4d` still segfaults for me: https://github.com/dscho/git/actions/runs/3538788474/jobs/5939977231#step:3:387 I hope that we can get this fixed very soon and am _very much_ in favor of fast-tracking the patches once we confirm that they fix the CI builds. Thanks, Dscho > The upgrade of runner images is in progress, and my public forked > repository still use 20.04 (focal) as "ubuntu-latest". > > Two patches in this series try to protect our CI in advance. > > New CI instance see below: > > * https://github.com/jiangxin/git/actions/runs/3532978329 > > -- > > Jiang Xin (2): > github-actions: run gcc-8 on ubuntu-20.04 image > ci: upgrade version of p4 > > .github/workflows/main.yml | 16 ++++++++++++---- > ci/install-dependencies.sh | 10 +++++----- > ci/lib.sh | 8 ++++---- > 3 files changed, 21 insertions(+), 13 deletions(-) > > -- > 2.39.0.rc0 > >
