Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip the memory resources test on K8s #522

Merged
merged 2 commits into from
Apr 5, 2022

Conversation

davewalter
Copy link
Member

What is this change about?

This PR updates the memory resource scaling test to be skipped when the infrastructure config option is set to Kubernetes.

Please provide contextual information.

This test fails often but is not worth changing now that cf-for-k8s is not under active development.

What version of cf-deployment have you run this cf-acceptance-test change against?

N/A

Please check all that apply for this PR:

  • introduces a new test --- Are you sure everyone should be running this test?
  • changes an existing test
  • requires an update to a CATs integration-config

Did you update the README as appropriate for this change?

  • YES
  • N/A

How should this change be described in cf-acceptance-tests release notes?

Skip the memory resource scaling test when the infrastructure config option is set to Kubernetes.

How many more (or fewer) seconds of runtime will this change introduce to CATs?

N/A

What is the level of urgency for publishing this change?

  • Urgent - unblocks current or future work
  • Slightly Less than Urgent

Tag your pair, your PM, and/or team!

@acosta11 @Birdrock @ctlong

davewalter and others added 2 commits April 4, 2022 17:38
- cf-for-k8s times out instead of generating the appropriate error
  message

Co-authored-by: Andrew Wittrock <awittrock@vmware.com>
Co-authored-by: Andrew Costa <ancosta@vmware.com>
- these are used to test changes to cf-smoke-tests-release
@@ -229,6 +229,9 @@ jobs:
OPS_FILES: |
operations/use-compiled-releases.yml
operations/use-internal-lookup-for-route-services.yml
operations/windows2019-cell.yml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why these changes?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't mean to include the pipeline changes in this PR. 😞

I switched the cf-smoke-tests-release pipeline to use the same environment for testing and that testing needs windows cells.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't follow.. if you didn't mean to include these pipeline changes why not remove them before merging this PR?

Copy link
Member Author

@davewalter davewalter Apr 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did mean to commit them. I just forgot to switch branch before doing so. IMHO, it wasn't important enough to update this PR and then create another PR with the CI change.

@davewalter davewalter merged commit a6e4d7a into develop Apr 5, 2022
@davewalter davewalter deleted the skip-memory-resource-test-on-k8s branch April 5, 2022 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants