test(filesystem): expand remote emulator integration coverage - #273
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
973075e to
371d62c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #273 +/- ##
==========================================
+ Coverage 59.45% 59.52% +0.07%
==========================================
Files 234 234
Lines 10977 10992 +15
==========================================
+ Hits 6526 6543 +17
+ Misses 4451 4449 -2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
49915a0 to
0d885f2
Compare
0d885f2 to
7963a06
Compare
|
Currently the branch seems to have conflicts, so the CI workflow didn't start at all after your recent adjustments. |
- Add xdist-safe, controller-managed S3, Azure, and GCS emulators with pinned images. - Cover remote formats, compression, globs, failures, native destination writes, cross-provider round trips, and S3 incremental loading. - Refresh S3 listings between repeated loads and support Azure destination connection strings. - Avoid emulator startup for unrelated targeted tests while keeping the fast lane Docker-free. - Document Azure connection-string authentication and repeated S3 load behavior.
7963a06 to
f7ac9d0
Compare
Summary
Scope
HttpSourcetofsspec.HTTPFileSystem#231, Filesystem: Migrate remote filesystem adapters from fsspec to pyarrow.fs (Azure Blob Storage, GCS, HDFS, S3) #233, and Filesystem: Clarifyfilesystem_incrementaloption ownership in fsspec sources #256.filesystem_incrementalbehavior remains tracked by Filesystem: Clarifyfilesystem_incrementaloption ownership in fsspec sources #256.Changes
Review
api_versiondocumentation and parsed pytest-target suggestions. Two scope/refactor suggestions were noted.Test plan