fix: set correct max test shards when arm devices are configured #2404
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current correct behavior:
-1
, AND ONLY physical devices are configured, Flank will adjust max-test-shards to the upper limit for physical devices-1
, AND ONLY virtual devices are configured, Flank will adjust max-test-shards to the upper limit for virtual devicesCurrent incorrect behavior:
-1
, and ARM devices are configured, Flank will adjust max-test-shards to the upper limit for virtual devices, which is currently higher than the documented upper limit for ARM devicesNew behavior:
-1
, and ARM devices are configured, Flank will adjust max-test-shards to the upper limit for ARM devicesFixes #2401