-
Notifications
You must be signed in to change notification settings - Fork 5
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 Tar_jll.jl to provide a GNU tar binary (instead of relying on the system tar) #51
Use Tar_jll.jl to provide a GNU tar binary (instead of relying on the system tar) #51
Conversation
Does |
🤔 In theory, you can use the Docker executor on Windows? |
I'm going to build a new |
Now it should be working |
Codecov Report
@@ Coverage Diff @@
## main #51 +/- ##
==========================================
- Coverage 79.01% 79.00% -0.01%
==========================================
Files 6 6
Lines 529 524 -5
==========================================
- Hits 418 414 -4
+ Misses 111 110 -1
Continue to review full report at Codecov.
|
Error during initialization of module |
It doesn't make sense it fails in 2 out of 6 jobs |
Maybe network issues, resulting in incomplete downloads that fail the subsequent hash check? |
What is going on here |
Bad things it seems. |
So it seems like the problem is when trying to instantiate the package environment inside of a Docker sandbox. |
In JuliaPackaging/Yggdrasil#3499 I added |
Huh. Yeah, maybe try removing that dependency, just to see if it fixes things? I also don't understand why that would be the problem, but 🤷 |
That'd be tomorrow though 💤 |
Actually, I take that back. It does look like the error is ultimately coming from |
Can you reproduce locally? |
Yes, thankfully. I ran the tests on an Linux x86_64 machine on which Docker is installed and on which I have Here is the log of the tests failing locally. The log looks basically the same as the CI logs. Click to expand:
|
Try Tar_jll 1.32 |
Yeah, if I set a compat entry of the form I left that code there (commented out), so that we can switch to it easily in the future. |
CI is green if I restrict Tar_jll to |
@staticfloat What do you think about merging this as-is, and then in the future we can upgrade to a new version of Tar_jll that supports I don't think there's a particular rush on upgrading the Tar_jll version. |
… system tar) Co-authored-by: Mosè Giordano <giordano@users.noreply.github.com>
@staticfloat @giordano What are your thoughts on this PR? My preference would be to merge this PR now as-is, and then update to the newest Tar_jll after we can solve the bug with loading libraries on musl. |
Thanks @staticfloat! Can we also get a new release of Sandbox.jl? |
For context, see all the issues we had because of `acl_jll` in JuliaContainerization/Sandbox.jl#51
* New version: Tar_jll v1.34.0+1 UUID: 9b64493d-8859-5bf3-93d7-7c32dd38186f Repo: https://github.com/JuliaBinaryWrappers/Tar_jll.jl.git Tree: f563224757d6c7bddf393435e96504259a517337 Registrator tree SHA: 8e1a5ac2695627143951512d700c7e3c445102ec * [Tar_jll] Yank `1.34.0+0` and remove dependency on `acl_jll` For context, see all the issues we had because of `acl_jll` in JuliaContainerization/Sandbox.jl#51 Co-authored-by: Mosè Giordano <mose@gnu.org>
Some systems (e.g. macOS) ship by default with a BSD
tar
that does not support the--owner
and--group
command-line options.This PR adds Tar_jll.jl as a dependency and uses it to provide a GNU
tar
so that we do not have to rely on the systemtar
.If Tar_jll is not supported on the platform, we fall back to the system
tar
.