-
Notifications
You must be signed in to change notification settings - Fork 135
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
MSFT_xArchive.EndToEnd.Tests.ps1 and MSFT_xArchive.Integration.Tests.ps1: Integration Tests Broken #457
Comments
As best as I can tell, these tests broke midway between #445 and #447. All tests passed for #445 (https://ci.appveyor.com/project/PowerShell/xpsdesiredstateconfiguration/build/6.0.1165.0), but started failing in #447 on, even though nothing in xArchive changed. Did something happen on the AppVeyor side between these two? |
Adding default resource maintainers (@kwirkykat and @mbreakey3), plus @johlju . Is there a way to log into a VM that's created as part of the AppVeyor build environment so that some manual debugging can be done? Since this issue can't be reproduced locally (at least as far as I can tell), it seems like a good way to debug this would be to get on one of these VM's and debug from there. Thanks. |
It can be enabled in the AppVeyor.yml. |
Ok, I setup an AppVeyor project and did some testing with my Fork. First I tried manually opening PowerShell on the build VM and running the problem Integration tests, and they run just fine. I then tried importing the AppVeyor module, and running Invoke-AppveyorTestScriptTask as per the AppVeyor.yml. The tests ran fine within that too. It seems the issue only occurs when the tests are running within/underneath 'Appveyor.BuildAgent.Interactive.exe'. I'm not really sure how to troubleshoot this further though. Any ideas? |
Reaching out to the community to get opinions on how to proceed with this issue while its being troubleshooted, as it's currently blocking a number of Pull Requests from getting merged, even though it's unrelated to those PR's. Should we continue to block all PR's until this is resolved? Should we ignore these and merge the PR's anyways? Should we disable the corresponding tests until we have a fix for them (that would be my vote)? Any other suggestions? |
This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close. |
It looks like my fix (improve how we detect if an archive is a folder or not) has resolved the integration test issues: But we really need to go through and start cleaning up this whole module and adopting the correct standards. Even though this isn't HQRM I still think the coding style should meet guidelines. So there is a lot of work to be done in that department (just check all the PSSA warnings). |
I've raised an issue over in PSDscResources to forward port these issues/fixes over there: |
😡 Turns out that this issue had already been resolved over in PSDscResources at some point (can't track down the issue), but the fix never back ported over here. So I've updated my fix to be a back port of that change. |
Fix Integration Test Failures in xArchive and General Code Quality improvements - Fixes #457
Details of the scenario you tried and the problem that is occurring
I'm not yet sure when it began, but all recent pull requests are failing during CI/CD due to issues in 'Tests\Integration\MSFT_xArchive.EndToEnd.Tests.ps1'. Specifically, it looks like various tests are failing due to file or folder copy issues. I cannot reproduce this issue locally (tried Win 10 / PS 5.1 and Win 2016 / PS 5). It appears something specific with AppVeyor may be causing these to fail.
The following requests and AppVeyor runs all show this issue. In all cases, no Archive related code was checked in, but the tests are failing anyways.
#447 / https://ci.appveyor.com/project/PowerShell/xpsdesiredstateconfiguration/builds/19890728
#448 / https://ci.appveyor.com/project/PowerShell/xpsdesiredstateconfiguration/builds/19922970
#450
https://ci.appveyor.com/project/PowerShell/xpsdesiredstateconfiguration/builds/19669492
Failed run output:
Version of the DSC module that was used ('dev' if using current dev branch)
dev
The text was updated successfully, but these errors were encountered: