-
-
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
Julia 1.10.0 fails REPL tests randomly #52739
Comments
aviatesk
added a commit
that referenced
this issue
Jan 29, 2024
The earlier test relied on the order of the method match list returned by `_methods_by_ftype`. However, particularly in cases where the `ambig=true` option is used, the match list isn't deterministic. This commit modifies it, similar to other pieces of code, so that it `any` to ensure the code does not depend on the implementation details of `ml_matches`. Fixes #52739.
aviatesk
added a commit
that referenced
this issue
Jan 29, 2024
The earlier test relied on the order of the method match list returned by `_methods_by_ftype`. However, particularly in cases where the `ambig=true` option is used, the match list isn't deterministic. This commit modifies it, similar to other pieces of code, so that it `any` to ensure the code does not depend on the implementation details of `ml_matches`. Fixes #52739.
Drvi
pushed a commit
to RelationalAI/julia
that referenced
this issue
Jun 7, 2024
The earlier test relied on the order of the method match list returned by `_methods_by_ftype`. However, particularly in cases where the `ambig=true` option is used, the match list isn't deterministic. This commit modifies it, similar to other pieces of code, so that it `any` to ensure the code does not depend on the implementation details of `ml_matches`. Fixes JuliaLang#52739.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Julia version 1.10.0 (official build, Linux version installed to a local user from an official *tar.gz) fails REPL tests randomly.
On the first run:
On the second immediate run:
On the third run you may or may not reproduce the error. For example, when I was writing this post the third run was successful. Sometimes, the first run is OK, the second or subsequent fail
The text was updated successfully, but these errors were encountered: