Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wait for container connection in service load test #21079

Closed

Conversation

kian-thompson
Copy link
Contributor

@kian-thompson kian-thompson commented May 14, 2024

Tinylicious is seeing lots of "OpRoundtripTime" errors around the time of initialization. We should wait until we connect to start sending the ops.

AB#7819

@github-actions github-actions bot added area: tests Tests to add, test infrastructure improvements, etc base: main PRs targeted against main branch labels May 14, 2024
@kian-thompson kian-thompson marked this pull request as ready for review May 15, 2024 00:59
@@ -256,6 +256,7 @@ async function runnerProcess(
container = await loader.resolve({ url, headers }, stashedOps);

container.connect();
await waitForContainerConnectionWithTimeout(container);
Copy link
Contributor

Choose a reason for hiding this comment

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

something like this already happens within the below test.run(runConfig, reset). if something is missed there, that would be a better place for it.

also, should we consider not logging op round trip perf when not connected? as this is a real scenario, and i don't think we would want to log errors when it happens in any case

@kian-thompson kian-thompson marked this pull request as draft May 15, 2024 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: tests Tests to add, test infrastructure improvements, etc base: main PRs targeted against main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants