Skip to content
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

BuildBundle-Linux CI jobs are failing with version GLIBC_2.28 not found #3321

Closed
adpaco-aws opened this issue Jul 3, 2024 · 1 comment · Fixed by #3322
Closed

BuildBundle-Linux CI jobs are failing with version GLIBC_2.28 not found #3321

adpaco-aws opened this issue Jul 3, 2024 · 1 comment · Fixed by #3322
Assignees
Labels
[C] Internal Tracks some internal work. I.e.: Users should not be affected.

Comments

@adpaco-aws
Copy link
Contributor

BuildBundle-Linux CI jobs are failing with version `GLIBC_2.28` not found as in this CI run. This seems to be caused by actions/checkout#1809 so it might be easier to just upgrade to v4.

@adpaco-aws adpaco-aws added the [C] Internal Tracks some internal work. I.e.: Users should not be affected. label Jul 3, 2024
@adpaco-aws adpaco-aws self-assigned this Jul 3, 2024
@adpaco-aws adpaco-aws changed the title BuildBundle-Linux CI jobs are failing with `version GLIBC_2.28 not found` BuildBundle-Linux CI jobs are failing with version GLIBC_2.28 not found Jul 3, 2024
@adpaco-aws
Copy link
Contributor Author

An upgrade to v4 doesn't do the trick (see #3322). This seems to happen with runner versions 2.316.1 and 2.317.0 but I don't know how we can avoid them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[C] Internal Tracks some internal work. I.e.: Users should not be affected.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant