Repository navigation
Add max-concurrency and device-location to mobile runs - #1
Merged
Merged
Conversation
The mobile API accepts both; the action sent neither, so every action-driven mobile run was one check at a time. The README claimed the location filter did not exist.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
max-concurrency, so a suite runs several checks at once, each on its own device. The action previously sent no value, which left every action-driven mobile run sequential regardless of what the installation allowed.device-locationto narrow auto-selection to a datacenter. The mobile API acceptssearch_criteria[location]; the README stated it did not exist.max-concurrencyfails locally rather than after the API has already saved a setup instruction and orphaned it.device-serialwarns and is dropped, matching how the other auto-selection inputs behave.Docs
The README gained a "How many at a time" section covering what caps concurrency (installation Device Quota, check count, free matching devices — lowest wins), that the quota is a ceiling rather than an override, and that each running check occupies an agent slot so going wider than the installation has slots just books idle devices.
timeout-secondsguidance now notes mobile wall time scales down with concurrency.