[Bug]: Crash in background worker test

[erimatnor]

What type of bug is this?

Crash

What subsystems and features are affected?

Background worker

What happened?

The crash seemed to occur when running the bgw_telemetry test.

TimescaleDB version affected

2.17-dev

PostgreSQL version used

16

What operating system did you use?

Ubuntu 24.04

What installation method did you use?

Source

What platform did you run on?

Other

Relevant log output and stack trace

#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x000072662c76f26e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x000072662c7528ff in __GI_abort () at ./stdlib/abort.c:79
#5  0x0000639224ef5b37 in ExceptionalCondition (conditionName=0x726620a1d19a "list_length(jobs) <= 1", 
    fileName=0x726620a1cfb8 "/home/enordstr/work/timescaledb/src/bgw/job.c", lineNumber=622) at assert.c:66
#6  0x00007266209b6f81 in ts_bgw_job_find_with_lock (bgw_job_id=1000, mctx=0x63922687c060, tuple_lock_mode=2, lock_type=TXN_LOCK, block=true, 
    got_lock=0x7ffd762e866f) at /home/enordstr/work/timescaledb/src/bgw/job.c:622
#7  0x00007266209b6fef in ts_bgw_job_get_share_lock (bgw_job_id=1000, mctx=0x63922687c060) at /home/enordstr/work/timescaledb/src/bgw/job.c:639
#8  0x00007266209bca69 in worker_state_cleanup (sjob=0x639226800748) at /home/enordstr/work/timescaledb/src/bgw/scheduler.c:207
#9  0x00007266209bcc2b in scheduled_bgw_job_transition_state_to (sjob=0x639226800748, new_state=JOB_STATE_SCHEDULED)
    at /home/enordstr/work/timescaledb/src/bgw/scheduler.c:262
#10 0x00007266209bdfe2 in check_for_stopped_and_timed_out_jobs () at /home/enordstr/work/timescaledb/src/bgw/scheduler.c:718
#11 0x00007266209be375 in ts_bgw_scheduler_process (run_for_interval_ms=86400000, bgw_register=0x726620a064a4 <ts_timer_mock_register_bgw_handle>)
    at /home/enordstr/work/timescaledb/src/bgw/scheduler.c:813
#12 0x0000726620a06f75 in ts_bgw_db_scheduler_test_main (fcinfo=0x8d12) at /home/enordstr/work/timescaledb/test/src/bgw/scheduler_mock.c:191
#13 0x0000639224bf2199 in StartBackgroundWorker () at bgworker.c:861
#14 0x0000639224bffa91 in do_start_bgworker (rw=0x639226799310) at postmaster.c:5765
#15 0x0000639224bf9214 in maybe_start_bgworkers () at postmaster.c:5989
#16 0x0000639224bfb600 in process_pm_pmsignal () at postmaster.c:5152
#17 0x0000639224bf939c in ServerLoop () at postmaster.c:1773
#18 0x0000639224bf824d in PostmasterMain (argc=8, argv=0x6392267211e0) at postmaster.c:1466
#19 0x0000639224aa768d in main (argc=8, argv=0x6392267211e0) at main.c:198

How can we reproduce the bug?

Seems random so not easy to reproduce.