Command to fully restart TestItemRunner.jl

[kbarros]

Sometimes TestItemRunner falls out of sync with a project. Is there a command to restart TestItemRunner without restarting the whole VSCode application?

Examples:

• TestItemRunner will detect new @testitems, but it appears that it won't remove missing ones. Is there a command to force it to rescan a project? This becomes particularly obvious when switching between different git branches with different sets of @testitems.
• In most cases, TestItemRunner correctly detects when types have changed and the Julia process needs to restart. But sometimes this detection fails, and the TestItemRunner process falls out of date. For example, in some cases when a function is removed, TestItemRunner will report that tests are passing when in fact that they should fail due to the missing function. (If this is not an already-known bug, let me know if you'd like a simple reproducer.).

My question/request: Is there a VSCode command (1) to restart the TestItemRunner process or (2) to force TestItemRunner to re-scan for @testitems? Thanks in advance.

[davidanthoff]

You can kill test runner processes on the Julia Workspace, they show up there.

All the things you describe sound like bugs to me, we should fix those!

[lmiq]

I found a situation which seems to be reproducible enough:

This minimal package has the issue: https://github.com/lmiq/TestTests.jl

If you run the tests there, Aqua will fail because of an unbound type parameter, which happens in this line:

f(;g::Union{H,Nothing}=nothing) where {H<:Function} = g(1) 
#f(;g) = g(1) 

If the first line there is commented and the second is uncommented, the error should disappear, but it doesn't, the test still fails with the same error message.

Killing the TestServer in the workspace solves the problem with that test.