XFAIL test_child_raises_parent_exits_cleanly with multiprocessing#1339
Merged
ogrisel merged 2 commits intojoblib:masterfrom Sep 15, 2022
Merged
Conversation
Codecov ReportBase: 94.00% // Head: 93.94% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #1339 +/- ##
==========================================
- Coverage 94.00% 93.94% -0.07%
==========================================
Files 52 52
Lines 7294 7294
==========================================
- Hits 6857 6852 -5
- Misses 437 442 +5
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Apparently this flaky test only fails for the non-default multiprocessing backend. While it would be nice to find a way to fix it, it seems particularly difficult to investigate.
Let's mark it as XFAIL for now while referencing the existing open issue #1086.