-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Some tests do not perform proper Module cleanup #11058
Copy link
Copy link
Closed
Labels
Issue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productResolution-FixedThe issue is fixed.The issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Quality-Testissues in a test or in test infrastructureissues in a test or in test infrastructure
Description
Metadata
Metadata
Assignees
Labels
Issue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productResolution-FixedThe issue is fixed.The issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Quality-Testissues in a test or in test infrastructureissues in a test or in test infrastructure
In CI we run several different test suites in the same PS runspace.
Some tests do Not cleanup after themselves, leaving loaded modules they were working with.
Sometimes this produces unexpected results and breaks subsequent tests.
Steps to reproduce
get-modulein the beginning of each test fileActual behavior
here is example output listing modules that are loaded in the beginning of an unrelated test file