Description of changes: We have fewer PRs nowadays so keeping a bunch of parallel sauce lab sessions available just for tests that are extremely unlikely to break doesn't make much sense. We still run these tests daily and on release, and they still can be run locally. We just need enough tests to sanity check that nothing explodes during a PR. I do not consider the content share tests to likely catch issues.
Testing:
N/A
Checklist:
Have you successfully run npm run build:release locally?
y
Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
n
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
n
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Issue #: None
Description of changes: We have fewer PRs nowadays so keeping a bunch of parallel sauce lab sessions available just for tests that are extremely unlikely to break doesn't make much sense. We still run these tests daily and on release, and they still can be run locally. We just need enough tests to sanity check that nothing explodes during a PR. I do not consider the content share tests to likely catch issues.
Testing:
N/A
Checklist:
Have you successfully run
npm run build:release
locally? yDo you add, modify, or delete public API definitions? If yes, has that been reviewed and approved? n
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved? n
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.