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

Extended Duration of Integration Tests Run #242

Open
so-sahu opened this issue Mar 19, 2024 · 1 comment
Open

Extended Duration of Integration Tests Run #242

so-sahu opened this issue Mar 19, 2024 · 1 comment
Assignees
Labels
bug Something isn't working prio-mid

Comments

@so-sahu
Copy link
Contributor

so-sahu commented Mar 19, 2024

Describe the bug
The integration-tests run time has been increasing steadily, now taking over 20 minutes. It seems that in some of the integration tests, no images are provided, resulting in the need to destroy the machine due to no OS. This, coupled with a high gracefulShutdownTimeout, as seen here, is causing the extended duration of the integration-tests run.

Proposed Solution
To improve the situation, machines should boot properly in integration tests so that the shutdown process can be triggered, ultimately leading to a shorter run duration for the integration tests.

@so-sahu so-sahu added the bug Something isn't working label Mar 19, 2024
@so-sahu so-sahu self-assigned this Mar 19, 2024
@lukas016
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working prio-mid
Projects
Status: In Progress
2 participants