-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
DUMMY: investigating Windows precompilation failure in 1.8.2 #4445
Conversation
Codecov ReportBase: 80.63% // Head: 80.66% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #4445 +/- ##
==========================================
+ Coverage 80.63% 80.66% +0.02%
==========================================
Files 30 30
Lines 7467 7494 +27
==========================================
+ Hits 6021 6045 +24
- Misses 1446 1449 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
As I recall, it appears to produce the same error. |
Nearest I can figure is that GR is failing to create the initial temporary file in Why it only seems to happen in CI so far, unclear. I'll keep poking. EDIT: Yep, if I deliberately create an empty file at Found a change in base/stream.jl between 1.8.1 and 1.8.2 - checking that - did not help LibUV was bumped from 1.42.0 to 1.44.2 between 1.8.1 and 1.8.2 |
4367bfa
to
cb52922
Compare
Irony: Using tmate to debug it on the CI machine, but it doesn't support scrolling, and the stack trace is too damn long 😆. And sadly resistant to my AbbreviatedStackTraces. |
9ebc1e2
to
111c502
Compare
Either GR is failing to create the file, perhaps via some change in libuv?, or it's being deleted before control returns to Plots. And unclear how precompilation environment differs from the normal REPL execution, where things work fine. Since LibUV is tightly bound to the Julia version, I don't think it'll be possible to debug that here. So next is to look at GR. Inquiring if there's an easy way to get debug information out of GR: sciapp/gr#161 Next obvious question, perhaps, is why this error doesn't show up in GR.jl's CI? Other question is how far back in Plots does this problem happen? The failure first appears in Plots v.1.34.0 - when this whole method of precompilation was introduced. |
I'm not sure how to reconcile the different approaches Plots takes to saving files via GR and how GR does it, to determine what might be going wrong in Plots'. Is it possible Plots is doing something not intended by GR? |
I agree that reproducing the issue in plain |
I think I've nailed it. EDIT: Nope.
Lines 671 to 672 in e9fb3b3
Crap. Replaced the wrong values. But got the same error. But it does suggest that GR is silently failing internally. |
The does show the limit of having a |
Did this ever come to any conclusion? I've been thinking of taking a look. |
I don't believe so. I didn't want to mess with GR so I stopped there. |
Superseded by #4617. |
I was curious about why Plots had an issue precompiling on Windows in JuliaLang/julia#46989, and I haven't been able to reproduce the issue on my system. So I'm trying to revert the workaround to see if the problem remains in the CI.