fix jupyter kernel test on Windows#97
Merged
alexander-penev merged 1 commit intocompiler-research:mainfrom May 15, 2024
Merged
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #97 +/- ##
=======================================
Coverage 53.66% 53.66%
=======================================
Files 15 15
Lines 600 600
=======================================
Hits 322 322
Misses 278 278 |
alexander-penev
approved these changes
May 15, 2024
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
3 participants
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.
This PR is a copy of #92 , but as one commit, as I was unable to squash the commits on the other PR. It makes changes such that the kernels can be parsed on Windows for jupyter_kernel_test , so they can now run. I have stopped the failing tests from running on Windows. @vgvassilev @alexander-penev @JohanMabille can one of you review this PR?