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

Use fuzz_tests_in_current_shard instead of computing the sharding again. #1477

Closed
wants to merge 1 commit into from

Conversation

copybara-service[bot]
Copy link
Contributor

Use fuzz_tests_in_current_shard instead of computing the sharding again.

This should be non-functional change for now, but it would smooth the transition to the unified execution model where each update-corpus invocation operates on a single test and fuzz_tests_in_current_shard contains exactly that test.

…gain.

This should be non-functional change for now, but it would smooth the transition to the unified execution model where each update-corpus invocation operates on a single test and fuzz_tests_in_current_shard contains exactly that test.

PiperOrigin-RevId: 703558945
@copybara-service copybara-service bot closed this Dec 10, 2024
@copybara-service copybara-service bot deleted the cl/703558945 branch December 10, 2024 14:44
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.

1 participant