-
Notifications
You must be signed in to change notification settings - Fork 213
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
General error when creating mulled containers #2442
Comments
Jupp, Singularity has problems with pulling the container. I assume that a recent Singularity version broke something but I had no time to look deeper into it. |
Hi, as quite some people depend on building mulled containers this way, would it maybe be an idea to pin the old Singularity version until the issue is solved? |
Hi @ggabernet and @bgruening
|
I fixed that upstream, just need to get the fix deployed here as well. Something changed in Singularity. Sorry, just need a bit more time. |
Hi @bgruening Thanks a lot for looking into this. Quick question: Once this is fixed, will the failed tests run automatically (OR) does the PR submitter need to do something to initiate the tests and the container build? Thanks once again. |
I will rerun the tests for you and if it turns green, merge it. Sorry for the inconvenience. |
Hi @bgruening , thanks a lot for fixing this! |
It should be fixed on master. There is now a small backlog of containers which I will try to resolve. If your PR is still failing, its likely that its the fault of the PR. Please wait another 24h or try to retrigger your PR on your own. Thanks for your patience. |
Hi,
I'm hitting an error when creating mulled containers that does not seem to be related to the specified dependencies, as it happens after a successful environment is built and all of the latest PRs are getting it, even the automated ones.
Here is the relevant part of the error message:
Here is the full error message:
https://github.com/BioContainers/multi-package-containers/pull/2439/checks
Several of the latest PRs are getting it including:
#2441
#2439
#2438
The text was updated successfully, but these errors were encountered: