You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run the test set in a isolated build environment (i.e., no external network) then they run sequentially in the same process and several fail due to bad interactions between them.
One of these failures is that the keywordargs.jl declaration
struct T20804{T}
y::Tend
(f::T20804)(;x=10) = f.y + x
causes the following in precompile.jl to not throw the expected exception
You can test these two are incompatible by just putting them back-to-back in a test.jl file and running them
using Test
struct T20804{T}
y::Tend
(f::T20804)(;x=10) = f.y + x
@test_throws ErrorException Core.kwfunc(Base.nothing)
$ julia test.jl
Test Failed at /build/test.jl:8
Expression: Core.kwfunc(Base.nothing)
Expected: ErrorException
No exception thrown
ERROR: LoadError: There was an error during testing
in expression starting at /build/test.jl:8
If you want to see it with the build system, and you don't have an isolated environment to build things in, I expect you can force tests to run sequentially by manually hacking test/runtests.jl
cd(@__DIR__) do
n = 1
if net_on
n = min(Sys.CPU_THREADS, length(tests))
n > 1 && addprocs_with_testenv(n)
LinearAlgebra.BLAS.set_num_threads(1)
end
skipped = 0
to not set n>1 (e.g., change net_on to false).
The text was updated successfully, but these errors were encountered:
Keno
added
bug
Indicates an unexpected problem or unintended behavior
test
This change adds or pertains to unit tests
labels
Feb 28, 2020
which has the same problem. Instead of using the shared method table for non-Functions this could be changed to use some function in Base that we're pretty sure won't have keyword arguments.
If you run the test set in a isolated build environment (i.e., no external network) then they run sequentially in the same process and several fail due to bad interactions between them.
One of these failures is that the keywordargs.jl declaration
causes the following in precompile.jl to not throw the expected exception
You can test these two are incompatible by just putting them back-to-back in a test.jl file and running them
If you want to see it with the build system, and you don't have an isolated environment to build things in, I expect you can force tests to run sequentially by manually hacking test/runtests.jl
to not set
n>1
(e.g., changenet_on
tofalse
).The text was updated successfully, but these errors were encountered: