1
76%
master: 76%

Ran 05 May 2026 10:10PM UTC

Files 19

Run time 0s

Badge

Embed ▾

Committed 05 May 2026 10:00PM UTC coverage: 75.435% (+0.07%) from 75.363%

Job # 25404692616.1

Build Type

push

github

Committed by

oleg-jukovec

Commit Message

tests: prevent leaked tarantool on bad start

Two related issues from #147 made test failures painful to diagnose:

1. When a test panicked, the spawned tarantool process was left
   running and kept its TCP port bound, so the next run failed with
   "address already in use" instead of the original test failure.

2. The defer/require ordering used in many tests was

       inst, err := test_helpers.StartTarantool(opts)
       defer test_helpers.StopTarantoolWithCleanup(inst)
       require.NoError(t, err)

   When StartTarantool returned a nil instance on error (the connect
   failure path returns nil after stopping the half-started process),
   the deferred cleanup ran on a nil pointer and panicked, hiding the
   real "Unable to start Tarantool" failure under a nil-deref stack.

Fix the first by setting Pdeathsig=SIGTERM on the tarantool command
on Linux via a new test_helpers.commandKillOnExit helper, with a
no-op fallback for other platforms (darwin has no Pdeathsig
equivalent — see the comment in cmd_other.go).

Fix the second by reordering every offending test site to assert
StartTarantool succeeded before deferring the cleanup. This is the
standard Go idiom and avoids growing a nil-guard inside the helper
that would mask further StartTarantool bugs.

Part of #147

Coverage Stats

3120 of 4136 relevant lines covered (75.44%)

10006.63 hits per line

tarantool / go-tarantool / 25404692616 / 1
76%
master: 76%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 25404692616.1

tarantool / go-tarantool / 25404692616 / 1 76% master: 76%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 25404692616.1

tarantool / go-tarantool / 25404692616 / 1
76%
master: 76%

README BADGES
x