-
-
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
Regression (change) in inference after SCC PR #39361
Labels
Milestone
Comments
vtjnash
added a commit
that referenced
this issue
Jan 23, 2021
This has actually been broken for a long time, so it only got noticed when it caused a regression. Fixes #39361
vtjnash
added a commit
that referenced
this issue
Jan 25, 2021
This has actually been broken for a long time, so it only got noticed when it caused a regression. Fixes #39361
KristofferC
pushed a commit
that referenced
this issue
Jan 26, 2021
KristofferC
pushed a commit
that referenced
this issue
Feb 1, 2021
ElOceanografo
pushed a commit
to ElOceanografo/julia
that referenced
this issue
May 4, 2021
This has actually been broken for a long time, so it only got noticed when it caused a regression. Fixes JuliaLang#39361
antoine-levitt
pushed a commit
to antoine-levitt/julia
that referenced
this issue
May 9, 2021
This has actually been broken for a long time, so it only got noticed when it caused a regression. Fixes JuliaLang#39361
staticfloat
pushed a commit
that referenced
this issue
Dec 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
#39116 caused the following change:
What is interesting is that when running it through the interpreter it still gives the older ("better") result
This caused a few packages to start failing in the backport branch (for example https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/7d1533d_vs_8240225/MultivariateBases.1.6.0-beta1-85c46c0116.log).
I'll put a 1.6 blocker on this for now, but I don't know if this is expected or how it should be assessed.
cc @vtjnash
The text was updated successfully, but these errors were encountered: