Skip to content
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

Remove @test_nowarn from tests #45

Open
KristofferC opened this issue Nov 9, 2021 · 1 comment · May be fixed by #46
Open

Remove @test_nowarn from tests #45

KristofferC opened this issue Nov 9, 2021 · 1 comment · May be fixed by #46

Comments

@KristofferC
Copy link

Failing the tests because of a single deprecation warning or anything getting emitted to stderr is very strong. This package fails tests, cf https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/e8caa27_vs_f23fc0d/StochasticDelayDiffEq.1.7.0-rc2-73a7a8e46fe.log

┌ Warning: dt <= dtmin. Aborting. There is either an error in your model specification or the true solution is unstable.
└ @ SciMLBase ~/.julia/packages/SciMLBase/x3z0g/src/integrator_interface.jl:345
SDDEProblem, solve: Test Failed at /workspace/srcdir/usr/share/julia/stdlib/v1.7/Test/src/Test.jl:806
  Expression: isempty(stderr_content)
   Evaluated: isempty("┌ Warning: dt <= dtmin. Aborting. There is either an error in your model specification or the true solution is unstable.\n└ @ SciMLBase ~/.julia/packages/SciMLBase/x3z0g/src/integrator_interface.jl:345\n")
Stacktrace:
 [1] top-level scope
   @ /opt/julia/share/julia/stdlib/v1.7/Test/src/Test.jl:445
 [2] include(mod::Module, _path::String)
   @ Base ./Base.jl:418
 [3] include(x::String)
   @ Main.##274 ~/.julia/packages/SafeTestsets/A83XK/src/SafeTestsets.jl:23
 [4] macro expansion
   @ ~/.julia/packages/StochasticDelayDiffEq/tnNkg/test/runtests.jl:3 [inlined]
 [5] macro expansion
   @ /opt/julia/share/julia/stdlib/v1.7/Test/src/Test.jl:1282 [inlined]
 [6] top-level scope
   @ ~/.julia/packages/StochasticDelayDiffEq/tnNkg/test/runtests.jl:3
@devmotion devmotion linked a pull request Nov 9, 2021 that will close this issue
@ChrisRackauckas
Copy link
Member

That just failed because of a real error 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants