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

CI broken? #18

Open
starcraft66 opened this issue Feb 14, 2023 · 4 comments
Open

CI broken? #18

starcraft66 opened this issue Feb 14, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@starcraft66
Copy link
Contributor

This is more of an inquiry about the general status of the project. I tried using this to download a binary-cached version of mongodb on aarch64-darwin and it started building from source. I haven't taken a detailed look at the actual CI jobs and what they are doing but they do seem to have been failing for like a month.

@starcraft66 starcraft66 added the bug Something isn't working label Feb 14, 2023
@adrian-gierakowski
Copy link

I'd be interested in exactly the same package :)

@starcraft66
Copy link
Contributor Author

I took a more detailed look at CI and it seems that the problem is that it takes more than 6 hours for the CI job to run so it timed out on the 2 darwin and arm linux builders (x86 linux finished just shy of the 6 hour limit) during its last run. Ironically, the darwin builds times out while building mongodb because it's such a massive package.

The 6 hour time limit makes sense for free SaaS runners but thankfully, that just seems to be the default for self-hosted runners and can be extended (see https://github.com/orgs/community/discussions/26679). I'll open a PR to make the jobs run for longer.

@starcraft66
Copy link
Contributor Author

Looks like this was just a partial fix, as now all of the builders barf when trying to run nix-eval-jobs due to glibcxx symbol issues. The sync job also fails due to another directory not existing on the runner. These errors seem to be coming from the actual runners and not anything in the repo. @zimbatm could you take a look?

@Algram
Copy link

Algram commented Jun 12, 2023

I'm just here to mention that this is happening again with the mongodb-4_4 and mongodb-6_0 packages again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants