| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Sorry if this sounds overly pedantic, but isn't this "skipping tests that segfault" rather than "fixing tests that segfault"? It's a completely reasonably path to skip these tests and then come back later to fix them (if they matter), but I would suggest changing the PR title / commit message.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
As a mathematician I have no right to call anyone pedantic under practically any circumstances. |
Sorry, something went wrong.
After this, Emscripten makes it all the way through the test suite when I run it locally.
|
Seems like I can remove a lot of these xfails if I set -sSTACK_SIZE=10mb instead of 5mb. |
Sorry, something went wrong.
|
Nevermind that is not true. |
Sorry, something went wrong.
There was a problem hiding this comment.
The set of changes all looks fine to me.
However, if this is going to be a common mode of failure for tests (which this PR seems to indicate it will be), I'd rather see it pulled into a utility decorator, analogous to requires_subprocess (e.g., requires_full_stack?) so that the skip message is consistent.
Sorry, something went wrong.
|
Okay @freakboy3742 I made a common method for the stack-overflow skips. I also updated the description according to @mdboom's complaint. I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @freakboy3742, @mdboom: please review the changes made to this pull request. |
Sorry, something went wrong.
There was a problem hiding this comment.
One possible cleanup that I should have found on my first pass. There's also a bunch of CI failures that I'm fairly sure are due to one misapplied test decorator.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
Okay, I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @mdboom, @freakboy3742: please review the changes made to this pull request. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM - thanks for those fixes!
Sorry, something went wrong.
There was a problem hiding this comment.
test_ast changes looks good to me.
Sorry, something went wrong.
|
If @mdboom doesn't come back to approve this, maybe you can merge it @freakboy3742? I think I addressed his comment... |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
After this, Emscripten makes it all the way through the test suite when I run it locally.