Skip to content

Conversation

@perazz
Copy link
Member

@perazz perazz commented Jun 4, 2024

Due to on-going issues with GCC-13 in the github runners, I suggest to temporarily deactivate GCC-13 from the CI.
See: fortran-lang/fpm#1043
cc: @jvdp1 @fortran-lang/stdlib

@jalvesz
Copy link
Contributor

jalvesz commented Jun 4, 2024

I saw in one of the comments that someone bumped to ubuntu-24.04 and gcc14 to keep an up-to-date build. I tested it here https://github.com/jalvesz/FSPARSE/actions/runs/9366790111/job/25785056275 by explicitly setting the ubuntu version in the matrix and it works. Maybe it could be useful then to drop gcc13 from the ubuntu-latest which is currently pointing to 22.04 and add one option with ubuntu-24.04 and gcc 14 ?

@perazz
Copy link
Member Author

perazz commented Jun 4, 2024

cc @jalvesz:

  • ubuntu-latest -> ubuntu-24.04
  • gcc-13 restored for all configurations, except macos-latest

@jalvesz
Copy link
Contributor

jalvesz commented Jun 4, 2024

Should the same change be done for the fpm CI yml script? (Even though it is not failing, but to be consistent)

@gnikit
Copy link
Member

gnikit commented Jun 8, 2024

I would strongly advise against moving to Ubuntu 24, the image is still in Beta.
image

The removal of GCC 13 was a side effect of GitHub wanting to remove dependencies to third-party PPAs, which is understandable.

If we wish to test against multiple versions of GCC we should use the setup-fortran Action instead of manually installing compilers or swapping runner images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants