-
-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: switch to ubuntu-22.04 image to avoid timeout #2730
Conversation
Since the older ubuntu-20.04 image based runs commonly time-out, here an attempt with the current ubuntu-22.04 image.
Mhh, this triggers unrelated other issues:
|
Probably caused by newer and stricter version of gcc and/or glibc. Following warnings are causing error (with -Werror):
|
|
Thanks so much, @nilason ! |
Yay, also the two Ubuntu CI runs finished successfully - no timeout! |
Currently the Ubuntu based builds are failing badly, just restarted 'GCC' to see if this PR has the same issue. Indeed it has. |
:-( |
actions/runner-images#6911 looks like being related to this. |
Both Ubuntu 20.04 and 22.04 images were updated Jan 9: |
Or this actions/runner-images#6913 |
By the look of it, it works again. |
Any objections to merge this PR? |
I have no objections, we have the CentOS runner for testing on older systems, no?. If this indeed solves the timeout issues -- even better. |
Yes and no:
However, we will check if the code compiles on the older Centos runner while - with this PR - running the tests on the recent Ubuntu runner which doesn't timeout. And keeping the old Ubuntu runner which mostly time-outs doesn't help much. |
Fair enough. Maybe we can try this for some time, to see if it consistently works on a newer system and revert to the 20.04 if it doesn't. |
So, let's try! Merging... |
* GitHub actions: update to current versions The GHA `ci.yml` and others show the warning _Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-python@v2, r-lib/actions/setup-r@v1, actions/upload-artifact@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/._ Additionally: - update the various actions - updates ubuntu-20.04 to ubuntu-22.04 (see also OSGeo/grass#2730) - sync Python to v3.10 - updates to super-linter:v4 - super-linter: enable markdown linting - use the real super-linter action instead of a container - super-linter.yml: do not mix VALIDATE=true and VALIDATE=false Co-authored-by: Nicklas Larsson <n_larsson@yahoo.com> Co-authored-by: Edouard Choinière <27212526+echoix@users.noreply.github.com>
Since the older ubuntu-20.04 image based runs commonly time-out: * update to the current ubuntu-22.04 image * rename scripts to reflect usage of ubuntu-22.04 image
* GitHub actions: update to current versions The GHA `ci.yml` and others show the warning _Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-python@v2, r-lib/actions/setup-r@v1, actions/upload-artifact@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/._ Additionally: - update the various actions - updates ubuntu-20.04 to ubuntu-22.04 (see also OSGeo/grass#2730) - sync Python to v3.10 - updates to super-linter:v4 - super-linter: enable markdown linting - use the real super-linter action instead of a container - super-linter.yml: do not mix VALIDATE=true and VALIDATE=false Co-authored-by: Nicklas Larsson <n_larsson@yahoo.com> Co-authored-by: Edouard Choinière <27212526+echoix@users.noreply.github.com>
Since the older ubuntu-20.04 image based runs commonly time-out: * update to the current ubuntu-22.04 image * rename scripts to reflect usage of ubuntu-22.04 image
Since the older ubuntu-20.04 image based runs commonly time-out, here an attempt with the current ubuntu-22.04 image.
See also: https://github.com/actions/runner-images