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

Windows 2022 VagrantPlaybookCheck jobs are taking 11 hours #3553

Open
sxa opened this issue May 5, 2024 · 1 comment
Open

Windows 2022 VagrantPlaybookCheck jobs are taking 11 hours #3553

sxa opened this issue May 5, 2024 · 1 comment

Comments

@sxa
Copy link
Member

sxa commented May 5, 2024

Ref: https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/OS=Win2022,label=vagrant/buildTimeTrend

This has a significant impact on testing speed, so we should look at whether this can be sped up. While I have not investigated yet if it's from a windows update cycle or Visual Studio installs we should perhaps try to optimise those for the default case.

Unfortunately we don't have time stamps in the logs so this will need to be run manually or just run a job and watch the progress of the log via the jenkins UI.

@sxa sxa changed the title WIndows 2022 VagrantPlaybookCheck jobs are taking 11 hours Windows 2022 VagrantPlaybookCheck jobs are taking 11 hours May 8, 2024
@sxa
Copy link
Member Author

sxa commented May 9, 2024

Running https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/1873/ with fast mode to see how that compares.

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

No branches or pull requests

1 participant