-
Notifications
You must be signed in to change notification settings - Fork 36
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
QML.jl failing on upcoming beta2 (and crashing for 1.10), though both seemingly false alarms... #196
Comments
Because of Line 18 in 8dc510d
|
Upgrading to CxxWrap 0.15 requires rebuilding also the |
Is this a bug or a feature request? If it is a bug, can it be fixed by updating |
Just tested QML 0.9.1 with Julia 1.10.5, and the tests pass. Therefore I close this issue. If there still is an issue with a different configuration, please comment and I will re-open. |
I assumed, wrongly, it's because of CxxWrap (v0.15.0) but it passes tests on its own:
https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/bdc7fb7_vs_bd47eca/CxxWrap.primary.log
https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/bdc7fb7_vs_bd47eca/QML.primary.log
Unless it's because for QML:
But then it's still a question, why isn't latest QML tested with all latest dependencies, such as CxxWrap, by PkgEval?
I see this when I install packages, I sometime get older versions (usually something blocking), and at least in one case got non-latest, but nothing was blocking upgrade to latest... I think it may just be a "bug" in Pkg, and fixing that might fix PkgEval.
Ideally of course older versions of CxxWrap would also work...
https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/bdc7fb7_vs_bd47eca/report.html
JuliaLang/julia#54112 (comment)
If older versions of CxxWrap are known to break on newer Julias (hus happened) then is there another workaround, changing in the registry so that for certain Julias at least some version needs to be installed? Because if even PkgEval fails, and Pkg doesn't install correctly, then this can for sure happen to regular users...
The text was updated successfully, but these errors were encountered: