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
This case might be too niche, but that i felt the need to record so we had the possibility written down.
As of #1763 being merged
AFAICT we have no way to disable deprecation warnings during tests.
It could be that these deprecation warnings make one's tests too slow to complete, and right now there is nothing that can be done about it.
There are a number of ways we could fix this, largely around differentiating between default and no.
For example: (for sake of example using strings and excluding validation)
function Pkg.test(name; depwarn=nothing)
if depwarn === nothing
depwarn = (Base.JLOptions().depwarn == 2 ? "error" : "yes")
end
#...
That way if the user passes in depwarn="no" then it would not read the JLOptions and would just stick with "no"
The text was updated successfully, but these errors were encountered:
This case might be too niche, but that i felt the need to record so we had the possibility written down.
As of #1763 being merged
AFAICT we have no way to disable deprecation warnings during tests.
It could be that these deprecation warnings make one's tests too slow to complete, and right now there is nothing that can be done about it.
There are a number of ways we could fix this, largely around differentiating between
default
andno
.For example: (for sake of example using strings and excluding validation)
That way if the user passes in
depwarn="no"
then it would not read theJLOptions
and would just stick with"no"
The text was updated successfully, but these errors were encountered: