-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
fix: workaround for git test workflow for Python 3.8 #1369
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1369 +/- ##
===========================================
- Coverage 84.07% 84.05% -0.02%
===========================================
Files 38 38
Lines 5305 5301 -4
===========================================
- Hits 4460 4456 -4
Misses 845 845 ☔ View full report in Codecov by Sentry. |
The previous point is still the root cause but the fix did not work. Thus, we now skip it in the workflow for 3.8. |
@@ -115,7 +115,7 @@ def tearDown(self) -> None: | |||
"""Tear down the test""" | |||
os.chdir(self.cwd) | |||
try: | |||
shutil.rmtree(self.workdir, ignore_errors=True) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I introduced this in another PR to fix this issue but it did not help. Hence, I removed it here again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lit
Our Python 3.8 tests kept failing due to temporary files not being deleted in our pytest setup.
This was because, for some unexplainable reason, oslo concurrency lock files were created after a pytest fixture closed. This pytext fixture was used in a parameterized pytest and even deleted the lock file itself. However, the lock files were re-created after the fixture finished.
As this only affects our git workflow and only for Python 3.8, I added a skip to the test that causes this problem, as far as I know.