1
75%
master: 76%

Ran 05 May 2026 09:13AM UTC

Files 19

Run time 1s

Badge

Embed ▾

Committed 05 May 2026 09:05AM UTC coverage: 75.387% (+0.1%) from 75.266%

Job # 25367568607.1

Build Type

Pull #587

github

Committed by

bigbes

Commit Message

tests: capture tarantool log tail in startup errors

When StartTarantool fails, the returned error gives only the connection
or exit reason ("exit status 1", "context deadline exceeded"), so a CI
failure required re-running the test locally to see why tarantool
actually refused to come up. Tarantool's own diagnostics — bad config,
port conflicts, missing modules, Lua errors during init — were written
to the child's stdout/stderr and silently dropped on the floor.

Wire a small ring buffer into Cmd.Stdout/Stderr that retains the last
50 lines, append it to the StartTarantool error on the two failure
paths (unexpected exit and connect failure), and expose the same tail
on TarantoolInstance for live tests.

Add test_helpers.DumpLogsIfFailed so a passing StartTarantool followed
by a later assertion failure can surface the captured log via t.Logf.
Intended idiom:

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

Buffer is safe for concurrent writes from exec.Cmd's two copy goroutines
and preserves a partial trailing line if the process exits without
flushing a newline.

Closes #147.

Pull Request Pull Request #587: tests: capture tarantool log tail in startup errors

Coverage Stats

3118 of 4136 relevant lines covered (75.39%)

10074.96 hits per line

tarantool / go-tarantool / 25367568607 / 1
75%
master: 76%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 25367568607.1

tarantool / go-tarantool / 25367568607 / 1 75% master: 76%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 25367568607.1

tarantool / go-tarantool / 25367568607 / 1
75%
master: 76%

README BADGES
x