-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Appveyor freezing during cmdlineargs test #11818
Comments
While this might be #7942, something caused this to get much more frequent, starting last night. Might be related to Line 88 in 5651bba
|
yay ! |
This may not be entirely accurate if the problem is intermittent, I'll try re-running the cmdlineargs test multiple times at the "good" entries below and see if it's consistent.
|
@vtjnash points out that the cmdlineargs test consists of starting julia many times, and #11640 makes windows build a .ji and not a .dll by default, making startup take much longer. So we could maybe fix it by telling the appveyor build to build sys.dll. Or make sys.dll the default, and only change it when building release packages. Either way. |
Yes, I would expect that change to make cmdlineargs slower - compare after https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.5999/job/kdn69hwhfqbv3vx8 (231 s) vs before https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.5959/job/t6gleq8mpnp123oo (41 s). It's freezing, not just slow. |
Unrelated, but PSA: because a day is not allowed to go by without julia breaking on appveyor in new and exciting ways, the new failure mode today as in https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.6008/job/0u8vmb335kfyc0bx was short rather than a timeout - at least it works through the backlog quicker than a timeout. The reason for today's new failure to compile was what happens when |
Oh, for crying out loud, that's broken too (╯°□°)╯︵ ┻━┻ |
Sometimes this has also been freezing in |
So is the conclusion that |
It makes the cmdlineargs test not take quite as long. I'm willing to close this as effectively a duplicate of #7942 though since I suspect it's the same problem. |
The first build against master where this happened is https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.5994/job/l01nwf0rwaedju0o, for 6ec7c21
I can reproduce locally, will try to see whether it's repeatable or intermittent (once I walk over to stata)
The text was updated successfully, but these errors were encountered: