We have a fastparquet pytest marker for tests that require fastparquet, and we have two such tests, but from a search in our code base, it doesn't seem that we include fastparquet anywhere in one of our CI test builds.
The two tests are:
test_fastparquet_cross_compatibility in the parquet tests, added in https://issues.apache.org/jira/browse/ARROW-6683 (I know that pandas has similar cross compat tests)test_fastparquet_read_with_hdfs in test_hdfs.py: ensuring fastparquet can use our HDFS filesystem -> this is something that fsspec / fastparquet can test themselves I think, and this is also in our legacy HDFS tests that we will remove once removing the legacy HDFS bindings
Given the above, we could also consider removing the tests alltogether (although adding fastparquet in one of the nightly builds should also be easy)
We have a
fastparquetpytest marker for tests that require fastparquet, and we have two such tests, but from a search in our code base, it doesn't seem that we include fastparquet anywhere in one of our CI test builds.The two tests are:
test_fastparquet_cross_compatibilityin the parquet tests, added in https://issues.apache.org/jira/browse/ARROW-6683 (I know that pandas has similar cross compat tests)test_fastparquet_read_with_hdfsin test_hdfs.py: ensuring fastparquet can use our HDFS filesystem -> this is something that fsspec / fastparquet can test themselves I think, and this is also in our legacy HDFS tests that we will remove once removing the legacy HDFS bindingsGiven the above, we could also consider removing the tests alltogether (although adding fastparquet in one of the nightly builds should also be easy)