This reverts commit a61fd31e2e.
Now that shippable has run once, it won't run the complete windows tests
anymore so we don't have to worry about any timeouts anymore.
* Divide Windows integration tests into 2 groups.
* Support `none` for `--changed-all-target`.
* Run 2 separate Windows groups on Shippable.
* Only run smoketest and minimal for the group1 job.
The default naming convention for patch branches created in
the GitHub UI when editing files is: {username}-patch-{number}
The default naming convention for revert branches created in
the GitHub UI when reverting a PR is: revert-{pr_number}-{pr_branch_name}
This exclusion will prevent Shippable from running on these
branches until a PR is created.
This will disable the integration tests for all network platforms &
modules, though the unit tests will still run.
This is needed while a large refactor of the networking code is done.
This should improve reliability of our jobs on Shippable.
The Shippable AMIs should already have the latest docker image,
per Shippable support, so pull doesn't provide any benefit for us.
* Turn mount test back on
* Mount tests need PRIVILEGED so turn that back on
Revert "Revert "Set PRIVILEGED=true for non_destructive tests. (#17733)" (#17738)"
This reverts commit dc0fb1c212.
* Add a needs_privileged tag so that we can skip mount tests on centos6
Some containers timeout on shippable tests when run with privileged.
Unfortunately, some tests require that in order to run. Tagging those
allows us to skip those tests on the platforms that timeout when we get
ready to run the integration test in shippable.
* Centos6 times out with PRIVILEGED set so remove that (will disable the mount tests on centos6)
* Remove false start
* Enable more integration tests for python 3.
* Split out python 3 integration tests.
Now that we're running more integration tests on python 3, the
tests are taking long enough that they warrant splitting out in
the same way the python 2 tests are split.