-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
TST- Fixing issue with test_parquet test unexpectedly passing #24480
Conversation
Codecov Report
@@ Coverage Diff @@
## master #24480 +/- ##
=======================================
Coverage 92.32% 92.32%
=======================================
Files 166 166
Lines 52298 52298
=======================================
Hits 48285 48285
Misses 4013 4013
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #24480 +/- ##
==========================================
- Coverage 92.32% 92.31% -0.01%
==========================================
Files 166 166
Lines 52328 52335 +7
==========================================
+ Hits 48310 48312 +2
- Misses 4018 4023 +5
Continue to review full report at Codecov.
|
pandas/tests/io/test_parquet.py
Outdated
@@ -201,7 +201,8 @@ def test_options_get_engine(fp, pa): | |||
|
|||
|
|||
@pytest.mark.xfail(is_platform_windows() or is_platform_mac(), |
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.
Can you try removing the xfail entirely? It looks like it may be unnecessary now.
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.
I did do that in another branch and it passed the CI tests of travis, but it seems there's discussion of pyarrow and fastparquet as well as windows causing problems? Not completely sure.
Edit: Also passed CI tests in azure
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.
add pyarrow
and fastparquet
to this build: https://github.com/pandas-dev/pandas/blob/master/ci/deps/azure-macos-35.yaml as these are not being tested. I suspect this will actually still fail. I think then this test needs to be conditionally skipped on older pyarrow / fastparquet versions. We could add another macosx build that is a bit more modern, or just relax the numpy on this build to have it install a more modern pyarrow.
@datapythonista do we have the xfails shows somewhere? e.g. https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=6035 |
I don't exactly understand the rationale behind the builds, but a modern Mac build sounds reasonable. Without know much about the builds we have, what would make sense to me is to have a "base" dependencies file, and have a build with the same conda deps in Linux, Windows and Mac. Happy to work on this if it makes sense. Regarding xfails, I wanted to standardize the output of all the builds in #23115 (which still needs a bit of work). Not sure what is the preferred output, I think we have |
Seems to be passing now. |
So to catch up a bit, we still need the xfail because of |
no i think this is ok now |
@jreback I have an unpublished branch that removes the xfail completely from both windows and mac. It seems to be passing the CI tests. Can you advise if we should take out the xfail completely? |
yeah might be good to try that |
Looks like removing the xfail works, seems whatever issue arose from running this test (old dependency maybe?) is gone now. |
Thanks @RjLi13! |
* upstream/master: DOC: Fixing broken references in the docs (pandas-dev#24497) DOC: Splitting api.rst in several files (pandas-dev#24462) Fix misdescription in escapechar (pandas-dev#24490) Floor and ceil methods during pandas.eval which are provided by numexpr (pandas-dev#24355) BUG: Pandas any() returning false with true values present (GH pandas-dev#23070) (pandas-dev#24434) Misc separable pieces of pandas-dev#24024 (pandas-dev#24488) use capsys.readouterr() as named tuple (pandas-dev#24489) REF/TST: replace capture_stderr with pytest capsys fixture (pandas-dev#24496) TST- Fixing issue with test_parquet test unexpectedly passing (pandas-dev#24480) DOC: Doc build for a single doc made much faster, and clean up (pandas-dev#24428) BUG: Fix+test timezone-preservation in DTA.repeat (pandas-dev#24483) Implement reductions from pandas-dev#24024 (pandas-dev#24484)
…strings * upstream/master: TST: Skip db tests unless explicitly specified in -m pattern (pandas-dev#24492) Mix EA into DTA/TDA; part of 24024 (pandas-dev#24502) DOC: Fix building of a single API document (pandas-dev#24506) DOC: Fixing broken references in the docs (pandas-dev#24497) DOC: Splitting api.rst in several files (pandas-dev#24462) Fix misdescription in escapechar (pandas-dev#24490) Floor and ceil methods during pandas.eval which are provided by numexpr (pandas-dev#24355) BUG: Pandas any() returning false with true values present (GH pandas-dev#23070) (pandas-dev#24434) Misc separable pieces of pandas-dev#24024 (pandas-dev#24488) use capsys.readouterr() as named tuple (pandas-dev#24489) REF/TST: replace capture_stderr with pytest capsys fixture (pandas-dev#24496) TST- Fixing issue with test_parquet test unexpectedly passing (pandas-dev#24480) DOC: Doc build for a single doc made much faster, and clean up (pandas-dev#24428) BUG: Fix+test timezone-preservation in DTA.repeat (pandas-dev#24483) Implement reductions from pandas-dev#24024 (pandas-dev#24484)
…-dev#24480) * Fixing issue with test_parquet passing
…-dev#24480) * Fixing issue with test_parquet passing
git diff upstream/master -u -- "*.py" | flake8 --diff
This pr aims to make the failing test_parquet not strict since it now passes at least on my machine of Mac 10.14 running the latest python 3.7 and conda.