SIGTERM test leaks stderr interrupt trace

PallHaraldsson commented 9 months ago

It's most certainly unrelated to my error, but I noticed this and no worker 28 apparently:

https://buildkite.com/julialang/julia-master/builds/31038#018c515e-2fcc-4fd3-bc6b-59debe1c2e34

      From worker 28:   [20881] signal 15: Terminated
      From worker 28:   in expression starting at none:0
      From worker 28:   epoll_wait at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
      From worker 28:   uv__io_poll at /workspace/srcdir/libuv/src/unix/epoll.c:236
      From worker 28:   uv_run at /workspace/srcdir/libuv/src/unix/core.c:400
      From worker 28:   ijl_task_get_next at /cache/build/tester-amdci5-10/julialang/julia-master/src/partr.c:477
      From worker 28:   poptask at ./task.jl:989
      From worker 28:   wait at ./task.jl:998
      From worker 28:   task_done_hook at ./task.jl:678
      From worker 28:   jfptr_task_done_hook_58822.1 at /cache/build/tester-amdci5-9/julialang/julia-master/julia-e52146150b/lib/julia/sys.so (unknown line)
      From worker 28:   _jl_invoke at /cache/build/tester-amdci5-10/julialang/julia-master/src/gf.c:2906 [inlined]
      From worker 28:   ijl_apply_generic at /cache/build/tester-amdci5-10/julialang/julia-master/src/gf.c:3088
      From worker 28:   jl_apply at /cache/build/tester-amdci5-10/julialang/julia-master/src/julia.h:2139 [inlined]
      From worker 28:   jl_finish_task at /cache/build/tester-amdci5-10/julialang/julia-master/src/task.c:327
      From worker 28:   start_task at /cache/build/tester-amdci5-10/julialang/julia-master/src/task.c:1317
      From worker 28:   unknown function (ip: (nil))
      From worker 28:   Allocations: 3532691 (Pool: 3532545; Big: 146); GC: 5
┌ Warning: rmprocs: process 1 not removed
└ @ Distributed /cache/build/tester-amdci5-9/julialang/julia-master/julia-e52146150b/share/julia/stdlib/v1.11/Distributed/src/cluster.jl:1049

I searched for "(28)" and just in case through all 28, so it seems strange. If this is a known problem or should be ignored since just a Warning you can close.

FYI, I also see (likely not a problem): ambiguous (11) | started at 2023-12-10T01:59:11.093 [..] From worker 11: Skipping Base.cwstring