-
-
Notifications
You must be signed in to change notification settings - Fork 415
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
MAINT: Split test file in two to find hanging test. #5680
Conversation
Codecov Report
@@ Coverage Diff @@
## main #5680 +/- ##
==========================================
- Coverage 89.81% 89.77% -0.05%
==========================================
Files 611 612 +1
Lines 51558 51562 +4
==========================================
- Hits 46309 46291 -18
- Misses 5249 5271 +22
... and 10 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Codecov Report
@@ Coverage Diff @@
## main #5680 +/- ##
==========================================
- Coverage 89.86% 88.53% -1.33%
==========================================
Files 615 616 +1
Lines 52474 52641 +167
==========================================
- Hits 47158 46608 -550
- Misses 5316 6033 +717
|
@Carreau What did we should do here? It is ready for merge, or you would like to rerun it a few times to try to trigger the problem? |
I've rebased. Even if it does not fail at least that should give us a hint if it's actually here in later PRs. |
The longer I think about this, it looks like merge this in the main could be a good idea, but it requires to put docstring that will describe when the file was split. |
It looks like some tests in test_qt_dims do hang sometime in CI. Though it's not clear which one with Pytest output. This split the test into two file approximatively where the hang happens, so we can narrow down the problem. This may help with napari#5443 maybe ?
How about this ? |
It looks like some tests in test_qt_dims do hang sometime in CI. Though it's not clear which one with Pytest output. This split the test into two file approximatively where the hang happens, so we can narrow down the problem. This may help with #5443 maybe ?
It looks like some tests in test_qt_dims do hang sometime in CI. Though it's not clear which one with Pytest output. This split the test into two file approximatively where the hang happens, so we can narrow down the problem. This may help with #5443 maybe ?
It looks like some tests in test_qt_dims do hang sometime in CI. Though it's not clear which one with Pytest output. This split the test into two file approximatively where the hang happens, so we can narrow down the problem. This may help with #5443 maybe ?
It looks like some tests in test_qt_dims do hang sometime in CI. Though it's not clear which one with Pytest output. This split the test into two file approximatively where the hang happens, so we can narrow down the problem. This may help with #5443 maybe ?
It looks like some tests in test_qt_dims do hang sometime in CI. Though it's not clear which one with Pytest output.
This split the test into two file approximatively where the hang happens, so we can narrow down the problem.
This may help with #5443 maybe ?