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

builder: use github as libisl mirror for ct-ng #504

Merged
merged 1 commit into from
Nov 23, 2024

Conversation

gnattu
Copy link
Member

@gnattu gnattu commented Nov 18, 2024

The previously used official SourceForge mirror is not reliable as the upstream hosting appears to be IP-blocking some GitHub runners’ IP addresses. Replace it with a self-hosted mirror on GitHub. This mirror is a repository created specifically for this purpose and can be updated if needed.

Changes

Issues

The old sourceforge mirror is not reliable and ct-ng is recommending
using github as the mirror for libisl
@gnattu gnattu requested a review from a team November 18, 2024 23:55
@nyanmisaka
Copy link
Member

I tried looking in the logs but couldn't find any errors related to libisl. Can you attach the relevant logs?

@gnattu
Copy link
Member Author

gnattu commented Nov 20, 2024

I tried looking in the logs but couldn't find any errors related to libisl. Can you attach the relevant logs?

It is from #501 where some CI nodes get 403 on downloading libisl. The problem here is that our CI took a very long time to finish and random error due to such issue is very very annoying. This is not the first time that our CI failed with package downloading issues and I'm not a big fan of it. Handbrake did something similar that archives all packages used in their own repo: https://github.com/HandBrake/HandBrake-contribs

@nyanmisaka nyanmisaka merged commit be7fced into jellyfin Nov 23, 2024
27 checks passed
@nyanmisaka nyanmisaka deleted the use-github-isl-mirror branch November 23, 2024 09:09
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