-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
MNT Use raise from in 19 modules #17835
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
Conversation
8f56e68
to
ad29136
Compare
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.
thanks @cool-RR , a few comments
a5de13e
to
df00a89
Compare
Hi @cool-RR codecov/patch check is unhappy: clicking on the Details link will give you all the information. For example, for one of the files |
@cmarmo Ah... We didn't do any of that testing in the previous PRs in this series. I'm a little reluctant to dig into scikit-learn's test architecture, because I went through a lot of files making the same change. Any chance I could get a pass on this? |
I haven't check in details where the codecov report has failed. A nice summary tells you which files are affected in your pull request.
Additional resources about tests are also available here.
I'm not the one deciding, sorry .. :). |
@NicolasHug Because I haven't gotten a reply on this PR for a long time, it now has a conflict. I can solve the merge conflict, but I first want to know whether you are even interested in accepted this PR, and whether there are any problems besides the merge conflict that would prevent this PR from being merged. |
I would be +1 for merging this. |
df00a89
to
13c0e6e
Compare
@thomasjpfan I'm seeing the CI is failing with this line: This doesn't seem related to my changes. Any idea why it's failing? How can I fix this? |
This should have been fixed with pytest-dev/pytest-xdist#287 It could be an issue with pytest 6.0 I'll look into it. |
So do we rerun? Do I need to push a new commit for that?
…On Fri, Aug 14, 2020, 19:08 Thomas J. Fan ***@***.***> wrote:
This should have been fixed with pytest-dev/pytest-xdist#287
<pytest-dev/pytest-xdist#287>
It could be an issue with pytest 6.0 I'll look into it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17835 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAN3SRW5UULPXEIHWXCRX3SAVOPVANCNFSM4OQYR2EA>
.
|
The issue will resolve with pytest-dev/pytest-cov#411 when There is no action we can take in this PR for now. I have a temporary fix at #17835 |
13c0e6e
to
ca06555
Compare
@thomasjpfan I assume that the |
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.
As for codecov, this means that some of these exceptions are not tested. I think I am okay with ignoring them in this PR.
ca06555
to
9d82cb8
Compare
@thomasjpfan Anything else needed before merging? |
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.
Thanks @cool-RR !
@NicolasHug This is the continuation of #17545
After we're done with this PR, I'll do another PR to fix the rest.