-
Notifications
You must be signed in to change notification settings - Fork 547
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
Use the Fedora :latest
container image again for CI testing
#4585
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
GitHub had issues with Fedora 40 when it was released. Hopefully this is not the case anymore. Closes: ceph#4585 Signed-off-by: Niels de Vos <ndevos@ibm.com>
GitHub had issues with Fedora 40 when it was released. Hopefully this is not the case anymore. Closes: ceph#4585 Signed-off-by: Niels de Vos <ndevos@ibm.com>
GitHub had issues with Fedora 40 when it was released. Hopefully this is not the case anymore. Closes: #4585 Signed-off-by: Niels de Vos <ndevos@ibm.com>
GitHub and the Fedora 40 container-image do not like each other. #4584 modifies the test-container image with a Fedora 39 base, instead of
:latest
.The problem is only seen on GitHub, not on laptops of different developers.
Logs of a failing CI jobs are attached: logs_23110536413.zip
The text was updated successfully, but these errors were encountered: