David Anthoff
David Anthoff
Ok, this is actually an upstream problem: https://github.com/JuliaTesting/TestEnv.jl/issues/59
TestItemRunner2 has a nice progress UI (two, in fact), but the problem with TestItemRunner is that we just print all the test output as it happens to stdout/stderr. So any...
It looks to me as if the Julia depot being used is a child folder of the package your are testing? This path `/builds/internal/MyPackage.jl/.julia/packages/TestItemRunner/Qioo0/src/TestItemRunner.jl` suggests that. So what happens then...
But apart from that, if we fix https://github.com/julia-vscode/TestItemRunner.jl/issues/41 then this should also address the situation here.
We can't in general limit things to the `test` folder as tests are allowed to be written inline in the package code. The easiest change would just be to adjust...
We should keep checking for a versions db update (and if there is one download it) to make sure the `add` command actually operates on the latest version info, but...
We are now getting a fair number of crash reports from the VS Code extension that look like this bug (at the moment it takes the top spot of "most...
That doesn't work yet, though :) I've just started the implementation, but it is not yet done.
Yes, agreed. At the moment the modules that are listed in the `setup` section are `import`ed into the test item module, but I think we should change that to `using`...
I think we should try to get the support for PRs in first. I'm not sure whether we can ever support arbitrary branches, because those are presumably not being built...