mhenke1 opened a new pull request #4496: Settle throttle before running the API GW Tests URL: https://github.com/apache/incubator-openwhisk/pull/4496 ## Description The API GW Test are able to drive OW into throttling. Though some code existed to throttle down these tests these tests were failing constantly on faster machines with 429 returned by OW. The test code controlling the throttle was correct in throttling the test execution in isolation, but was of course not able to overview invocations for the given namspace that do happen before tests were executing. Since this limitations does naturally exist, this change simplifies down the throttling logic to enhance code maintainability and introduces a wait period before executing the tests to ensure that the API GW test do not run into throttling driven by prior invokes in the same namespace. ## Related issue and scope - [ ] I opened an issue to propose and discuss this change (#????) ## My changes affect the following components - [ ] API - [ ] Controller - [ ] Message Bus (e.g., Kafka) - [ ] Loadbalancer - [ ] Invoker - [ ] Intrinsic actions (e.g., sequences, conductors) - [ ] Data stores (e.g., CouchDB) - [x] Tests - [ ] Deployment - [ ] CLI - [ ] General tooling - [ ] Documentation ## Types of changes - [x] Bug fix (generally a non-breaking change which closes an issue). - [ ] Enhancement or new feature (adds new functionality). - [ ] Breaking change (a bug fix or enhancement which changes existing behavior). ## Checklist: - [x] I signed an [Apache CLA](https://github.com/apache/incubator-openwhisk/blob/master/CONTRIBUTING.md). - [x] I reviewed the [style guides](https://github.com/apache/incubator-openwhisk/wiki/Contributing:-Git-guidelines#code-readiness) and followed the recommendations (Travis CI will check :). - [ ] I added tests to cover my changes. - [ ] My changes require further changes to the documentation. - [ ] I updated the documentation where necessary.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
