540e992e08
Automatic merge from submit-queue Faster test <!-- Checklist for submitting a Pull Request Please remove this comment block before submitting. 1. Please read our [contributor guidelines](https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md). 2. See our [developer guide](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md). 3. If you want this PR to automatically close an issue when it is merged, add `fixes #<issue number>` or `fixes #<issue number>, fixes #<issue number>` to close multiple issues (see: https://github.com/blog/1506-closing-issues-via-pull-requests). 4. Follow the instructions for [labeling and writing a release note for this PR](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes) in the block below. --> In attempting to troubleshoot flakes with this test case I actually wanted to understand how it worked. There's some poor comments that need work. I added some additional output which may or may not help in debugging the flakes. I doubt this fixes the flake. My major concern is the 'refactor' I did of the test case to batch up runs by sub-test-case. As it stood there was a 200ms pause between each sub, so they should not have interfered with each other. Now they are just started as fast as possible, but only 20 run at a time before moving on to the next 20. I am not sure if I am violating the ethos of the original test case. Runs on my computer are down from 2m40s -> 40s. Getting rid of the arbitrary client limiting brings it down to ~12 seconds. 11 to fetch the image and <1 to actually run the tests against the proxies. I can add a zero to the number of loops if you want to hit it harder. It would result in 10x as much text output though. []() |
||
|---|---|---|
| .. | ||
| component/scheduler/perf | ||
| e2e | ||
| e2e_node | ||
| fixtures/pkg/kubectl/cmd/apply | ||
| images | ||
| integration | ||
| kubemark | ||
| soak | ||
| utils | ||
| .gitattributes | ||
| OWNERS | ||
| test_owners.csv | ||