Skipping precompilation in VSCode test item framework

Tooling VS Code
,
1

My current workflow is having a project environnement in which I dev the package that I currently develop, ModelPredictiveControl.jl, and I include additional dependencies for the development. I also use the test item framework of VS Code, which is very nice to execute only one unit test.

The problem is every time I modify the code of my package (a modification supported by Revise), ModelPredictiveControl.jl needs to be precompiled at each execution of the unit test, which is long. Is there a way to opt out precompilation in the test item framework ? I tried to put a LocalPreferences.toml with:

[ModelPredictiveControl]
precompile_workload = false

in my project environnement for development, but it seems that it is ignored by the test item framework process.

3 Likes
2

Bumping the issue. The precompilation is really slow in Julia v1.12, so I would prefer to skip it for my own package when I execute my tests. Is it normal that the LocalPreferences.toml is ignored in the test item framework and VS code ?

edit: It’s weird because it seems that there is a first fast precompilation occuring, which is the typical behavior of LocalPreferences.toml file, but a second very slow one just after. Here’s a screenshot of the “Julia Test Process” log:
image