Service bindings test flake fix [179005915] #505
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* The expected output wasn't always available in the cf push logs. This is a more reliable implementation. [#179005915] Co-Authored-By: Bruce Ricard <bricard@vmware.com> Co-Authored-By: Peter Chen <pchen@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this change about?
Fixes a credhub test that fails intermittently.
Please provide contextual information.
179005915
What version of cf-deployment have you run this cf-acceptance-test change against?
latest
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
If you are introducing a new acceptance test, what is your rationale for including it CATs rather than your own acceptance test suite?
CATs should validate common operator workflows.
CATs is not a regression test suite.
CATs is run by every component team to validate their releases before promotion.
How should this change be described in cf-acceptance-tests release notes?
Fixes a credhub test that fails intermittently.
How many more (or fewer) seconds of runtime will this change introduce to CATs?
Maybe 10 seconds as the test polls for output. There's a 3-minute timeout if the test fails.
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@bruce-ricard @peterhaochen47