Check process start command for successful buildpack_cache usage instead #823
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.
Are you submitting this PR against the develop branch?
yes
What is this change about?
This test verifies that buildpacks can successfully use the buildpack cache.
Currently it does this by pushing and curling a one-line bash app. Recently, it's been flaky. Here are a few examples of flakes (though there are many others):
https://concourse.wg-ard.ci.cloudfoundry.org/teams/main/pipelines/cf-deployment/jobs/experimental-cats-cflinuxfs4/builds/168
https://ci.capi.land/teams/main/pipelines/capi/jobs/leia-azure-storage/builds/976
The issue is the start command seems to be set correctly, and the app is returning 502's/404's other errors for some reason. However, this test is not about how an app performs when running, it's about the staging/compilation process, so we opted to just check the process's start command for the same information.
What version of cf-deployment have you run this cf-acceptance-test change against?
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?
N/A
How many more (or fewer) seconds of runtime will this change introduce to CATs?
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@xandroc