specify timeout for gazelle manifest test #817
Merged
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.
Fixes #802
PR Checklist
Please check if your PR fulfills the following requirements:
I think this doesn't apply here, but LMK if there's something you want me to do.
Ditto
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Manifest test timeout is not set. Whatever it defaults to is too long, at least for my manifests, and bazel complains.
Issue Number: #802
What is the new behavior?
manifest test timeout is set to "short"
Does this PR introduce a breaking change?
In theory if someone's manifest test takes too long to run, this could break them.
In practice this seems very unlikely.
LMK if you want me to make this an option instead.
Other information