Attempt to fix the mock libnvme test so it works in GitHub actions & autopkgtest #404
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Different Python test frameworks manage Python processes differently when running tests. When running
python3 -m unittest
for instance, it looks like the same process executes all the tests. Therefore when one test module T1 imports a module, the module is not re-imported if needed by T2.This causes issues with test-defs.py which tries to mock the libnvme module. Indeed, when it is previously imported by staslib, the mocked libnvme module does not get re-imported.
This is an attempt to fix the test by removing staslib and staslib.defs from the imported modules before executing the test.