Skip to content

running: fix watchdog tests with race detector#1252

Open
sssciel wants to merge 1 commit intomasterfrom
g.rybakov/tntp-6356-fix-watchdog-data-races
Open

running: fix watchdog tests with race detector#1252
sssciel wants to merge 1 commit intomasterfrom
g.rybakov/tntp-6356-fix-watchdog-data-races

Conversation

@sssciel
Copy link
Contributor

@sssciel sssciel commented Mar 8, 2026

Watchdog tests completed with datarace warning with go test race detector enabled. This was because there was unsafe access to the proccess_controller.

Closes TNTP-6356

@sssciel sssciel requested review from elhimov and oleg-jukovec March 8, 2026 17:41
@sssciel sssciel force-pushed the g.rybakov/tntp-6356-fix-watchdog-data-races branch from 2ca8f8e to 2da1c10 Compare March 8, 2026 17:48
Watchdog tests completed with datarace warning with go test race
detector enabled. This was because there was unsafe access to the
proccess_controller.

Closes TNTP-6356
@sssciel sssciel force-pushed the g.rybakov/tntp-6356-fix-watchdog-data-races branch from 2da1c10 to 27fee44 Compare March 10, 2026 09:18
inst.setTarantoolLog(cmd)

// Start an Instance.
inst.mu.Lock()
Copy link
Contributor

@psergee psergee Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current approach raises questions. We are protecting only a single member of inst, even though the cluster instance employs the exact same process controller initialization code without any locking. Is this a test-specific fix for race conditions, rather than a comprehensive thread‑safety mechanism for the instances API?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants