This PR updates the flags specified in the run-cats task to use the new versions of the Ginkgo v2 CLI and updates the slow spec threshold to be a Golang time duration instead of a number of seconds. A new TIMEOUT parameter has been introduced to allow CI jobs to change the default Ginkgo timeout, which is now applied to the entire test suite run, instead of each individual test suite. It defaults to 2 hours, instead of the Ginkgo default of 1 hour.
[ ] introduces a breaking change (other users will need to make manual changes when this is released)
Did you update the README as appropriate for this change?
[ ] YES
[x] N/A
How should this change be described in release notes?
The Ginkgo CLI flags specified in the run-cats task have been updated to use the new versions of v2. The slow spec threshold has been updated to be a Golang time duration instead of a number of seconds. A new TIMEOUT parameter has been introduced to allow CI jobs to change the default Ginkgo timeout, which is now applied to the entire test suite run, instead of each individual test suite. It defaults to 2 hours, instead of the Ginkgo default of 1 hour.
What is the level of urgency for publishing this change?
What is this change about?
This PR updates the flags specified in the run-cats task to use the new versions of the Ginkgo v2 CLI and updates the slow spec threshold to be a Golang time duration instead of a number of seconds. A new
TIMEOUT
parameter has been introduced to allow CI jobs to change the default Ginkgo timeout, which is now applied to the entire test suite run, instead of each individual test suite. It defaults to 2 hours, instead of the Ginkgo default of 1 hour.Please provide contextual information.
Related to https://github.com/cloudfoundry/cf-acceptance-tests/pull/543
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
How should this change be described in release notes?
The Ginkgo CLI flags specified in the run-cats task have been updated to use the new versions of v2. The slow spec threshold has been updated to be a Golang time duration instead of a number of seconds. A new
TIMEOUT
parameter has been introduced to allow CI jobs to change the default Ginkgo timeout, which is now applied to the entire test suite run, instead of each individual test suite. It defaults to 2 hours, instead of the Ginkgo default of 1 hour.What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@ctlong