-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 functional tests in Buildkite constantly fail #9476
Comments
This may be related (similar container issues where we can't run our specs on containers) to why we have most of our testing disabled in the omnibus pipeline on internal Chef Software buildkite. https://github.com/chef/chef/blob/master/omnibus/omnibus-test.ps1#L94-L97 We need integration, functional and unit testing working on windows there, and need to have the chocolatey testing enabled. https://github.com/chef/chef/blob/master/omnibus/omnibus-test.sh#L160-L161 Similarly on *nix we need to have those tests re-enabled. |
We need to be running all unit, functional and integration tests in all test stages, and need to be running them as root, and that probably means NOT on any containers -- which is why I dumped that comment into this issue, because I suspect that containers are probably at least the first problem we will run into with re-enabling those tests. |
with the new win-2019 ami including ruby 2.6 + 2.7 we just needed to ensure we were using privileged |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Our windows functional tests are basically broken. They run on a shared system and fight each other / fail when they try to write / delete the same files. We need to get to a point where this job can reliably run and gets our tests green.
The text was updated successfully, but these errors were encountered: