Extension is updated?

Tooling VS Code
1

I noticed that a version 1.146.2 of the VS Code extension was released a few days ago. Is there a summary of what’s updated?

I’m still pinning myself to 1.127.2, since the version after that broke test-running (see VS Code won't run tests anymore). If that’s supposed to be fixed now, I’ll try the new version.

2 Likes
2

I tried out the 1.146.2 release today, so far it seems like it’s fixed the testing bugs from 1.140.

3

I spoke too soon, I’m seeing hangs again. At least this time there are some errors in the “Test Tesults” panel - starting out like so:

[91165] signal (15): Terminated: 15
in expression starting at /Users/kwilliams/.vscode/extensions/julialang.language-julia-1.146.2/scripts/packages/TestItemControllers/testprocess/app/testserver_main.jl:19
[ Info: Julia test item process launching
[ Info: Julia test item process launching
[ Info: Julia test item process launching
[ Info: Julia test item process launching
[ Info: Julia test item process launching
[ Info: Julia test item process launching
[ Info: Julia test item process launching
[ Info: Julia test item process launching
[ Info: Julia test item process launching
nnable
Stacktrace:
  [1] error(s::String)
    @ Base ./error.jl:35
  [2] schedule(t::Task, arg::Any; error::Bool)
    @ Base ./task.jl:871
  [3] schedule
    @ ./task.jl:863 [inlined]
  [4] uv_writecb_task(req::Ptr{Nothing}, status::Int32)
    @ Base ./stream.jl:1166
  [5] poptask(W::Base.IntrusiveLinkedListSynchronized{Task})
    @ Base ./task.jl:999
  [6] wait()
    @ Base ./task.jl:1008
  [7] uv_write(s::Base.PipeEndpoint, p::Ptr{UInt8}, n::UInt64)
    @ Base ./stream.jl:1048
  [8] unsafe_write(s::Base.PipeEndpoint, p::Ptr{UInt8}, n::UInt64)
    @ Base ./stream.jl:1120
  [9] unsafe_write
    @ ./io.jl:698 [inlined]
 [10] write(s::Base.PipeEndpoint, a::Vector{UInt8})
    @ Base ./io.jl:721
 [11] handle_message(logger::Logging.ConsoleLogger, level::Base.CoreLogging.LogLevel, message::Any, _module::Any, group::Any, id::Any, filepath::Any, line::Any; kwargs...)
    @ Logging ~/.julia/juliaup/julia-1.10.9+0.aarch64.apple.darwin14/share/julia/stdlib/v1.10/Logging/src/ConsoleLogger.jl:178
 [12] handle_message(logger::Logging.ConsoleLogger, level::Base.CoreLogging.LogLevel, message::Any, _module::Any, group::Any, id::Any, filepath::Any, line::Any)
    @ Logging ~/.julia/juliaup/julia-1.10.9+0.aarch64.apple.darwin14/share/julia/stdlib/v1.10/Logging/src/ConsoleLogger.jl:106
 [13] #invokelatest#2
    @ ./essentials.jl:892 [inlined]
 [14] invokelatest
    @ ./essentials.jl:889 [inlined]
 [15] macro expansion
    @ ./logging.jl:377 [inlined]
 [16] temp_cleanup_purge(; force::Bool)
    @ Base.Filesystem ./file.jl:549
 [17] temp_cleanup_purge
    @ ./file.jl:537 [inlined]
 [18] (::Base.var"#951#952")()
    @ Base ./initdefs.jl:366
 [19] _atexit(exitcode::Int32)
    @ Base ./initdefs.jl:428
  Activating new project at `/var/folders/d5/xj384ymn2r551n6yk4mwl2ch0000gp/T/jl_Txhadu`
   Resolving package versions...
kevent at /usr/lib/system/libsystem_kernel.dylib (unknown line)
unknown function (ip: 0x0)
Allocations: 80911676 (Pool: 80807110; Big: 104566); GC: 67
kevent at /usr/lib/system/libsystem_kernel.dylib (unknown line)
unknown function (ip: 0x0)
Allocations: 103573488 (Pool: 103438497; Big: 134991); GC: 63
┌ Warning: Failed to clean up temporary path "/var/folders/d5/xj384ymn2r551n6yk4mwl2ch0000gp/T/jl_OHsqO7"
│ ErrorException("schedule: Task not runnable")
└ @ Base.Filesystem file.jl:549
schedule: Task not runnablekevent at /usr/lib/system/libsystem_kernel.dylib (unknown line)
unknown function (ip: 0x0)
Allocations: 105242613 (Pool: 105112657; Big: 129956); GC: 75
┌ Warning: Failed to clean up temporary path "/var/folders/d5/xj384ymn2r551n6yk4mwl2ch0000gp/T/jl_wqlEA9"
│ ErrorException("schedule: Task not runnable")
└ @ Base.Filesystem file.jl:549
schedule: Task not runnablekevent at /usr/lib/system/libsystem_kernel.dylib (unknown line)
unknown function (ip: 0x0)
Allocations: 131856809 (Pool: 131687481; Big: 169328); GC: 71
kevent at /usr/lib/system/libsystem_kernel.dylib (unknown line)
unknown function (ip: 0x0)
Allocations: 137510072 (Pool: 137327213; Big: 182859); GC: 103
kevent at /usr/lib/system/libsystem_kernel.dylib (unknown line)
unknown function (ip: 0x0)
Allocations: 90945099 (Pool: 90830937; Big: 114162); GC: 62
...

So I’ll be reinstalling 1.127.2.

1 Like
4

Hm, that actually looks like a Julia bug to me… What Julia version are you using?

Also, there is a newer version of the extension as a pre-release out right now (v1.147) and in general I’m pushing out new versions there a lot that fix more and more test item stuff, its the thing I’m focused on right now. So maybe ideally at the moment try the pre-release versions to get the latest test item fixes. But I don’t think your error would be explained/fixed by the newer version…

1 Like
5

I’m using 1.10.9+0.aarch64.apple.darwin14 for my project, but I think VS Code is finding 1.11.5+0.aarch64.apple.darwin14 on my machine and using that for the test daemon processes? I’m not quite sure how to tell.

[EDIT] Actually I see Logging ~/.julia/juliaup/julia-1.10.9+0.aarch64.apple.darwin14 in the error output, so I guess it’s using my juliaup default of 1.10.9.