-
Notifications
You must be signed in to change notification settings - Fork 6
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
SparseConnectivityTracer: non-boolean used in boolean context #1883
Labels
core
Issues related to the computational core in Julia
Comments
visr
added a commit
that referenced
this issue
Oct 8, 2024
visr
added a commit
that referenced
this issue
Oct 8, 2024
visr
added a commit
that referenced
this issue
Oct 8, 2024
We have ``` install-julia = "juliaup add 1.10.5 && juliaup override unset && juliaup override set 1.10.5" ``` But in #1883 we can see (@evetion can see) that the Julia tests are still run using Julia 1.11, which is the new stable release that came out today. Rather than trying to find out what exactly goes wrong with the override, this just sets it when we start julia, so we can release.
@evetion noticed the Julia tests were running the just released julia 1.11.0. I made #1889 to address that. Testing locally with 1.11 and an updated Manifest.toml I can reproduce the issue running e.g. the HWS model. Might need fixing in https://github.com/adrhill/SparseConnectivityTracer.jl since it is surprising that |
visr
added a commit
that referenced
this issue
Oct 8, 2024
This allowed it to pick up Julia 1.11, leading to #1883.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just saw this randomly pop up in an unrelated PR: https://github.com/Deltares/Ribasim/actions/runs/11237297981/job/31239411451?pr=1881#step:5:629
Strange because main is green. Is this non-deterministic? Doesn't seem like it, #1882 now also hits it.
The text was updated successfully, but these errors were encountered: