Skip to content

Navigation Menu

Sign in
Sign up

test(pair-relay): drop self-declared duplicate test_cancellation_immediate - #7403

Open
rebekz wants to merge 1 commit into
block:main from
kafi-labs:upstream-fix/drop-duplicate-timeout-test
Open

test(pair-relay): drop self-declared duplicate test_cancellation_immediate #7403
rebekz wants to merge 1 commit into
block:main from
kafi-labs:upstream-fix/drop-duplicate-timeout-test

Conversation

@rebekz

@rebekz rebekz commented Sep 6, 2026

Copy link
Copy Markdown

Problem

test_cancellation_immediate in crates/buzz-pair-relay/tests/integration.rs flakes under parallel load and passes in isolation.

It is a duplicate — and the source says so itself:

/// 42. Connection closes promptly after 120 s (virtual time).
/// Explicit duplicate of test 9 with a slightly different assertion style.

In practice even the "different assertion style" is not different. Both tests are identical: start_relay, connect, advance(121s), yield_now, assert_closed. The name is also misleading — it tests a 120-second timeout, not immediate cancellation.

Fix

Delete the duplicate. test_120s_timeout (test 9) remains the canonical virtual-time coverage, so no coverage is lost.

Verification

test_120s_timeout passes after the deletion, exit 0. Nothing else in the file is touched.

Note, not addressed here

The same file declares another self-described duplicate a few lines below:

/// 43. ... Explicit duplicate of test 34 with a different connection state.

Left alone deliberately to keep this patch minimal — flagging it in case it is also worth pruning.

🤖 Generated with Claude Code

Remove test_cancellation_immediate, which upstream documents as an explicit duplicate of test 9 and implements identically. test_120s_timeout remains the canonical virtual-time coverage.
Signed-off-by: Fitra Kacamarga <fitra.19@gmail.com>
rebekz requested a review from a team as a code owner September 6, 2026 01:16

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 3c7f288c60d67df78577b237e27c3dfc8831aaa1...c03757a1591b2479f45b22954248cdf6f109da78.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review c03757a1591b2479f45b22954248cdf6f109da78 to authorize a new review.
Any previous review applies only to its recorded range.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

AltStyle によって変換されたページ (->オリジナル) /