Skip to content

Conversation

@bneradt
Copy link
Contributor

@bneradt bneradt commented Nov 6, 2025

For production traffic simulation, Proxy Verifier by default runs
through the specified connections in parallel. But for our end to end
tests, that hardly ever makes sense. Rather we want the tests to
deterministically run through each specified connection sequentially.
This patch does so by passing --thread-limit 1 as a default option to
the Proxy Verifier client in the client extension. Many tests were
specifying this already anyway, so this saves some burden on client
configuration for each of the test descriptions.

@bneradt bneradt added the AuTest label Nov 6, 2025
@bneradt bneradt self-assigned this Nov 6, 2025
@bneradt bneradt added this to the 10.2.0 milestone Nov 6, 2025
@bneradt bneradt changed the title Make --thread-limit 1 the default for verifier-client processes autest: --thread-limit 1 by default for Proxy Verifier Nov 6, 2025
For production traffic simulation, Proxy Verifier by default runs
through the specified connections in parallel. But for our end to end
tests, that hardly ever makes sense. Rather we want the tests to
deterministically run through each specified connection sequentially.
This patch does so by passing --thread-limit 1 as a default option to
the Proxy Verifier client in the client extension. Many tests were
specifying this already anyway, so this saves some burden on client
configuration for each of the test descriptions.
@bneradt bneradt force-pushed the pv_single_threaded branch from 9509633 to 874d640 Compare November 6, 2025 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant