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

Don't unnecessarily shard a single-run test #1738

Merged
merged 1 commit into from
Feb 7, 2022

Conversation

pmeenan
Copy link
Contributor

@pmeenan pmeenan commented Feb 4, 2022

and added a setting to disable test sharding.

The main impact this has for a single-run test is that the agent will send the first and repeat view results back together instead of incrementally. For multi-run tests with the setting turned on it lets the agent collect the full test result for possible edge-processing before sending it back.

and added a setting to disable test sharding.
@vibaldem
Copy link
Contributor

vibaldem commented Feb 4, 2022

Are there any considerations to make for private instances where the number of runs and the resulting size of the upload may get quite large?

@pmeenan
Copy link
Contributor Author

pmeenan commented Feb 5, 2022 via email

@pmeenan
Copy link
Contributor Author

pmeenan commented Feb 5, 2022 via email

Copy link
Contributor

@tkadlec tkadlec left a comment

Choose a reason for hiding this comment

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

Looking solid to me!

@tkadlec tkadlec merged commit 75b8537 into catchpoint:master Feb 7, 2022
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.

3 participants