Repository navigation
Add --priority for maestro, espresso and xcuitest - #67
Open
jochen-testingbot wants to merge 1 commit into
Open
jochen-testingbot wants to merge 1 commit into
jochen-testingbot wants to merge 1 commit into
Conversation
high, normal (default) or low for maestro, espresso and xcuitest, sent as `priority` on the run API. Higher priority starts first, then the oldest; it does not take slots from other accounts or raise the parallel limit.
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
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.
--priority high|normal|low: where the runs go in your own queue while they wait for a free parallel slot. High starts before normal, normal before low, then oldest first. It does not take slots from other accounts or raise the parallel limit. This is the same model asmaestro cloud --priorityin Maestro CLI 2.12.priorityonPOST /:id/runfor all three providers, and shown in--dry-runpayloads.Invalid --priority value (urgent). Use one of: high, normal, low.Server side: testingbot/web#444. Until that is deployed, the API ignores the field and runs keep today's order.
Tests: 890 passed (new: option parsing, payload for all 3 providers, not sent by default). README rows and CHANGELOG updated.