Failing during Setup Coverage build step

[BIGWALDOR]

Hey there,

We're currently experiencing a weird issue on our GitHub Hosted CI pipeline where the Setup Coverage build step keeps failing. I'm no CI expert by any means so a little guidance on how I can debug this further and resolve it would be much appreciated.

Please advise if there is any other bits of information I could share to help resolve this.

GitHub Runner Environment:
OS: Ubuntu 24.04
Laravel: 11.4
PHP: 8.2 with Xdebug

Here's the screenshot:

[shivammathur]

@BIGWALDOR
If you are using shivammathur/node images, please wait for a couple of hours for a new build to complete. The build earlier today failed.

[BIGWALDOR]

@shivammathur I'm using the shivammathur/setup-php package in my CI, not shivammathur/node. I am still experiencing this issue, where the package fails each time when trying to start/complete the Setup Coverage script step. (see screenshot).

[shivammathur]

@BIGWALDOR Please run it with shivammathur/setup-php@more-verbose instead of v2 and provide me the complete logs.

[BIGWALDOR]

@shivammathur apologies for the delay - here's the logs I've downloaded from GitHub:
0_laravel-tests.txt

Let me know if this helps.

[shivammathur]

@BIGWALDOR Based on the logs, your os is ubuntu 20.04 which is no longer supported by this action since 2.33.0 and ppa:ondrej/php as of yesterday.

Please upgrade your ubuntu version to 22.04 or 24.04.

See #939 and oerdnj/deb.sury.org#2243

[BIGWALDOR]

Thanks for your time to help debug this - I'll look into this further.

Weird though 🤔 The workflow is configured to run on ubuntu-latest so it should be running ubuntu:24.04.

[BIGWALDOR]

@shivammathur sorry to bother you - I reviewed the Set Up Job log and can see that the CI is provisioning Ubuntu 24.04.

I don't understand why the setup-php step uses Ubuntu 20.04 though.

1_Set up job.txt

[shivammathur]

Most likely that is because you are using kirschbaumdevelopment/laravel-test-runner, My recommendation would be to run it directly on the GitHub runner and remove the container from your workflow.

[BIGWALDOR]

I see - I looked into this and I believe that is the root cause indeed. Again, appreciate your guidance with this issue.

[rainysia]

same on my side.

[winner343]

me too

[shivammathur]

Please provide me the logs by running it using shivammathur/setup-php@more-verbose