SNOW-3243341: Python e2e tests for pyarrow and pandas support#532
SNOW-3243341: Python e2e tests for pyarrow and pandas support#532sfc-gh-asolarski wants to merge 1 commit intomainfrom
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
sfc-gh-asolarski
force-pushed
the
03-17-snow-3243341_python_e2e_tests_for_pyarrow_and_pandas_support
branch
7 times, most recently
from
a9a7150 to
08e6aec
Compare
| fail-fast: false | ||
| matrix: | ||
| os: [ubuntu-latest, windows-11-arm] | ||
| py: ["3.9", "3.10", "3.11", "3.12", "3.13", "3.14"] |
There was a problem hiding this comment.
This will be conflicting with @sfc-gh-pczajka changes. I would suggest to sort this out as the firs step.
.github/workflows/test-python.yml
Outdated
| - extras: "no-extras" | ||
| extras_suffix: "" | ||
| hatch_test_cmd: "all-cov" | ||
| hatch_test_args: "--ignore=tests/e2e/pandas" |
There was a problem hiding this comment.
Personally I would consider having hatch run test-no-pandas instead of juggling args in CI definition
There was a problem hiding this comment.
In fact, we could consider having dedicated hatch env for pandas. This way we may be able to siplify the CI definiition to single command name
sfc-gh-asolarski
force-pushed
the
03-17-snow-3243341_python_e2e_tests_for_pyarrow_and_pandas_support
branch
5 times, most recently
from
62cdf8a to
99e9433
Compare
sfc-gh-asolarski
force-pushed
the
03-17-snow-3243341_python_e2e_tests_for_pyarrow_and_pandas_support
branch
from
99e9433 to
9a2fe15
Compare
2 participants
No description provided.