You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After merging #3171 noticed there was a CI failure running on master but it's not specifically related to that PR. It's happening on the ARM runner:
/home/pgjdbc/actions-runner/externals/node20/bin/node: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/pgjdbc/actions-runner/externals/node20/bin/node)
Something changed either in our action versions or the github runner itself (my guess...) to use a more recent node version (v20 v.s. v18) which requires a newer libc. My guess is that the github runner itself has changed (i.e. the code that github sends to the runner to do runner stuff...) as the v18 node version has been EOL since last year.
To resolve this I think the ARM version needs to have it's OS upgraded. Otherwise we're going to see repeated failures in CI.
The text was updated successfully, but these errors were encountered:
After merging #3171 noticed there was a CI failure running on
master
but it's not specifically related to that PR. It's happening on the ARM runner:Something changed either in our action versions or the github runner itself (my guess...) to use a more recent node version (v20 v.s. v18) which requires a newer libc. My guess is that the github runner itself has changed (i.e. the code that github sends to the runner to do runner stuff...) as the v18 node version has been EOL since last year.
To resolve this I think the ARM version needs to have it's OS upgraded. Otherwise we're going to see repeated failures in CI.
The text was updated successfully, but these errors were encountered: