Skip to content

test: count this query's rbtc-tip-flush thread - #1284

Closed
rearden-grok[bot] wants to merge 1 commit into
masterfrom
test/tip-flush-thread
Closed

rearden-grok[bot] wants to merge 1 commit into
masterfrom
test/tip-flush-thread

Conversation

@rearden-grok

@rearden-grok rearden-grok Bot commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Coverage on e19d0db5 (run 40738545456) failed tip_flush::two_ibd_flushes_share_one_named_thread with left: 1, right: 0 on the post-drop comm count. The test job passed.

That assert counts every rbtc-tip-flush in the process. The query suite runs in one process, so another query's barrier thread is still visible after this query joins its own. The worker now publishes an alive count and its Linux tid, and the test reads those.

cargo test --workspace, ./scripts/ci-os-smoke.sh, clippy -p rbitcoin-query --all-targets, cargo deny check, and ./scripts/ast-grep.sh passed locally.

The suite scanned every comm in the process. Under coverage another
query still had the barrier thread after this one dropped, so
two_ibd_flushes_share_one_named_thread failed while the test job passed.
@rearden-grok

rearden-grok Bot commented Oct 28, 2026

Copy link
Copy Markdown
Contributor Author

The same pin is already on #1217 (test: a tip flush counts its own thread). two_ibd_flushes_share_one_named_thread reads this query's alive count and Linux tid there, including the {pid}/task/{tid} parse of /proc/thread-self. Closing this as duplicate.

@rearden-grok rearden-grok Bot closed this Oct 28, 2026
@rearden-grok
rearden-grok Bot deleted the test/tip-flush-thread branch October 28, 2026 18:22
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.

0 participants