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

Increase CAPVCD ClusterReady timeout to 40Min #548

Merged
merged 2 commits into from
Nov 19, 2024
Merged

Increase CAPVCD ClusterReady timeout to 40Min #548

merged 2 commits into from
Nov 19, 2024

Conversation

njuettner
Copy link
Member

@njuettner njuettner commented Nov 19, 2024

Unfortunately the last CP nodes longer 😞, so we need to adjust it one more time.

@njuettner njuettner requested review from a team as code owners November 19, 2024 14:25
@njuettner
Copy link
Member Author

I'm merging it, I'd like to see if the tests are finally passing we have a follow up issue to address that it takes too long.

@njuettner njuettner merged commit 38086bd into main Nov 19, 2024
1 of 3 checks passed
@njuettner njuettner deleted the sadjk branch November 19, 2024 14:39
@tinkerers-ci
Copy link

tinkerers-ci bot commented Nov 19, 2024

cluster-test-suites

Run name pr-cluster-test-suites-548-cluster-test-suites7vr8c
Commit SHA b538121
Result Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites


Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

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.

1 participant