GH-36629: [CI][Python] Skip dask tests due to our non-nanosecond changes in arrow->pandas conversion

[raulcd]

Rationale for this change

Due to the changes on #33321 a dask test started failing.

What changes are included in this PR?

Skip the test in the meantime

Are these changes tested?

Yes, with crossbow

Are there any user-facing changes?

No

• Closes: [CI][Python] Dask integration nightly jobs fail on dask.dataframe.io.tests.test_parquet::test_pandas_timestamp_overflow_pyarrow #36629

[raulcd]

@github-actions crossbow submit dask

[github-actions]

⚠️ GitHub issue #36629 has been automatically assigned in GitHub to PR creator.

[raulcd]

@jorisvandenbossche as you suggested I skipped the test, is there an issue we should create to follow it up?

[github-actions]

Revision: 6364629

Submitted crossbow builds: ursacomputing/crossbow @ actions-6841a6feb4

Task	Status
test-conda-python-3.11-dask-latest
test-conda-python-3.11-dask-upstream_devel

[jorisvandenbossche]

@github-actions crossbow submit dask

[github-actions]

Revision: 6364629

Submitted crossbow builds: ursacomputing/crossbow @ actions-f91d54dfef

Task	Status
test-conda-python-3.11-dask-latest
test-conda-python-3.11-dask-upstream_devel

[jorisvandenbossche]

The upstream_devel one is now segfaulting while running the tests. But I assume that is a new / separate issue, because I see it's also happening in the nightly ones. Will try to investigate or check when this started.

[jorisvandenbossche]

is there an issue we should create to follow it up?

Let's create a reminder to remove the skip again, yes -> #36666

[j-bennet]

fyi dask/dask#10412.

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 3bdbd0d.

There was 1 benchmark result indicating a performance regression:

• Commit Run on ursa-i9-9960x at 2023-07-22 22:33:08Z
  • engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-02, scale_factor=1

The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them.