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

e2e-test: default delete timeout per cloudprovider #1705

Conversation

mkulke
Copy link
Contributor

@mkulke mkulke commented Feb 20, 2024

fixes #1704

The Azure tests will not reliably pass the deletion tests within 60s. Added a per-cloudprovider default setting and made the deletionWithin param mandatory for the TestCase struct.

fixes confidential-containers#1704

The Azure tests will not reliably pass the deletion tests within 60s.
Added a per-cloudprovider default setting and made the deletionWithin
param mandatory for the TestCase struct.

Signed-off-by: Magnus Kulke <magnuskulke@microsoft.com>
Copy link
Member

@stevenhorsman stevenhorsman left a comment

Choose a reason for hiding this comment

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

The code looks good to me, so I've triggered the libvirt tests. Thanks

Copy link
Member

@surajssd surajssd left a comment

Choose a reason for hiding this comment

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

looks ok

@mkulke mkulke merged commit 2628573 into confidential-containers:main Feb 20, 2024
29 checks passed
@mkulke mkulke deleted the mkulke/add-per-cloudprovider-timeouts-to-e2e-test branch February 20, 2024 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test_e2e_libvirt Run Libvirt e2e tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

azure: ci e2e timing out
3 participants