-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
[BUG] Limited GR support for Linux Aarch64 #2877
Comments
Do you have network connection? It tries to download the GR binaries but fails. |
Yes I do, that's why the curl 404 error seems strange. coz@nav-jetson:~$ ping -c4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=32.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=14.6 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=118 time=24.0 ms
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 14.634/22.887/32.601/6.538 ms
That's probably what I am going to do atm. Though would have been nice to do both on the device. |
Have you managed to resolved this? I am having similar issue on Nvidia Jetson board. GR doesn't work, plotly works though. |
I found the same issue building on Aarch64 (on EC2). I'll test later on Raspberry Pi as well. It looks to me like maybe the GR install is trying to download an asset that doesn't exist for Aarch64. |
@AbelHo @pschmied Thanks for your feedback. The issue persists. It does seem like it's a problem related to GR trying to download something and failing as @pschmied pointed out. The thing in question is the asset behind this link. If you examine the assets found in the release page of GR under v0.49.0 there is no such file, so it's only logical that it fails. However, it seems GR supports Debian Aarch64 starting from v0.52.0. I'm going to rename the issue to "Limited GR support for Linux Aarch64" to be more general and hope there would be a GR compat bump for Aarch64 in Plots.jl. Would be happy if in the meantime someone suggests how to resolve this locally. |
What do you mean by that? Current Plots version has compat entries for GR versions till 0.53. |
You are right @BeastyBlacksmith. However this happens when I try to Building GR → `~/.julia/packages/GR/cRdXQ/deps/build.log`
┌ Error: Error building `GR`:
│ --2020-12-18 13:36:54-- https://github.com/sciapp/gr/releases/download/v0.49.0/gr-0.49.0-Linux-aarch64.tar.gz
│ Resolving github.com (github.com)... 140.82.121.3
│ Connecting to github.com (github.com)|140.82.121.3|:443... connected.
│ HTTP request sent, awaiting response... 404 Not Found
│ 2020-12-18 13:36:54 ERROR 404: Not Found
.
.
. It still tries to download the GR v0.49.0 files judging by the URL. EDIT: Plots version v1.9.1 |
Can you try to explicitly add GR v0.53 befor adding Plots? |
Good idea, but it still fails. I called Building GR → `~/.julia/packages/GR/RlE5Y/deps/build.log`
┌ Error: Error building `GR`:
│ --2020-12-18 15:31:36-- https://github.com/sciapp/gr/releases/download/v0.53.0/gr-0.53.0-Linux-aarch64.tar.gz
│ Resolving github.com (github.com)... 140.82.121.3
│ Connecting to github.com (github.com)|140.82.121.3|:443... connected.
│ HTTP request sent, awaiting response... 404 Not Found
│ 2020-12-18 15:31:37 ERROR 404: Not Found.
.
.
. |
Thats likely a bug in the build script of GR.jl then. @jheinen |
The issue seems to be mentioned not too long ago in here. Subsequently fixed by this commit. So I added the master branch of GR.jl via |
Hi, It seems this fixes the problem on ARM, is there a reason why this hasn't been released in a month? |
Are you really on GR#master? |
[91a5bcdd] + Plots v1.10.6 Attaching the log file just in case. The full Julia REPL output
|
Could you pls try |
Same problem:
|
The tar file you are looking for is available both on GitHub and gr-framework.org - same for the stable releases. I have absolutely no idea, why you can't download them. |
As far as I can see the installation procedure complains about not being able to find the file on disk AFTER it is successfully downloaded. I can only assume that the file is downloaded to one placed and then the installer tries to find it in a different place. |
On a recent update of Plots.jl my arm64 deployment also broke with this error begin
import Pkg
Pkg.build("Plots")
end
Update: I deleted the GR artifact, removed the Plots dependency (working in Pluto) and readded it again. Hint came from this discourse comment - thank you so much @t-bltg. This seemed to have helped. So it seems the GR artifact can go corrupt, which of course should never happen for such a stable package as Plots. |
Ideally the checksum for the artifact is checked after download and if it doesn't match the file is deleted and either a retry happens or you'd get a helpful error, but that would need to be handled by Pkg (don't know what the current behaviour is). |
Yeah, I've seen lots of |
I have no idea/explanation why the GR artifact could go corrupt. We started supporting In addition, an X virtual framebuffer is no longer mandatory as a display server for GR3. |
thank you for your extra help. Unfortunately I cannot reproduce the issue on my side and am very astonished, that somehow such an old GR version (0.49 seems to be 3 years old) came onto my julia 1.9 docker with fresh installed environments. Summary: Sorry for hijacking this old issue. It was fitting my issue search, even with this precise version 0.49. I guess nothing useful is to be added, but that some weird GR installation issues still appear for Aarch64 today. Luckily very rarely, but still. |
Details
I'm trying to get Plots up and running on the Nvidia Jetson to plot some GPU vs CPU benchmarks. I tried asking around on the discourse, however the post doesn't seem to get any traction. The crux of the issue is what happens after
add Plots
:Some failed attempts to fix this:
Backends
This bug occurs on ( insert
x
below )Versions
Plots.jl version: v1.5.6
Backend version (
]st -m
):Output of
versioninfo()
:The text was updated successfully, but these errors were encountered: