You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2022/09/27 10:17:00 UTC
[jira] [Commented] (ARROW-17853) [Python][CI] Timeout in test_dataset.py::test_write_dataset_s3_put_only
[ https://issues.apache.org/jira/browse/ARROW-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609951#comment-17609951 ]
Antoine Pitrou commented on ARROW-17853:
----------------------------------------
The gdb-level backtrace looks like this:
{code}
#0 0x00007fa7adf61ad3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x55f7fdacdb28)
at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55f7fdacdad8, cond=0x55f7fdacdb00) at pthread_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x55f7fdacdb00, mutex=0x55f7fdacdad8) at pthread_cond_wait.c:655
#3 0x00007fa7a8b28b47 in std::condition_variable::wait<arrow::ConcreteFutureImpl::DoWait()::{lambda()#1}>(std::unique_lock<std::mutex>&, arrow::ConcreteFutureImpl::DoWait()::{lambda()#1}) (this=0x55f7fdacdb00, __lock=..., __p=...) at /opt/conda/envs/arrow/x86_64-conda-linux-gnu/include/c++/10.4.0/condition_variable:111
#4 0x00007fa7a8b2771f in arrow::ConcreteFutureImpl::DoWait (this=0x55f7fdacda90) at /arrow/cpp/src/arrow/util/future.cc:154
#5 0x00007fa7a8b27b0a in arrow::FutureImpl::Wait (this=0x55f7fdacda90) at /arrow/cpp/src/arrow/util/future.cc:189
#6 0x00007fa79224f60d in arrow::Future<arrow::internal::Empty>::Wait (this=0x7ffe2b877770) at /arrow/cpp/src/arrow/util/future.h:385
#7 0x00007fa79224c23a in arrow::Future<arrow::internal::Empty>::result() const & (this=0x7ffe2b877770) at /arrow/cpp/src/arrow/util/future.h:356
#8 0x00007fa792248510 in arrow::Future<arrow::internal::Empty>::status (this=0x7ffe2b877770) at /arrow/cpp/src/arrow/util/future.h:372
#9 0x00007fa792290c66 in arrow::dataset::FileSystemDataset::Write (write_options=..., scanner=...) at /arrow/cpp/src/arrow/dataset/file_base.cc:436
#10 0x00007fa79255f3dd in __pyx_pf_7pyarrow_8_dataset_10_filesystemdataset_write (__pyx_self=0x0, __pyx_v_data=0x7fa78edbc220, __pyx_v_base_dir=0x7fa78edc0700,
__pyx_v_basename_template=0x7fa78f024520, __pyx_v_filesystem=0x7fa78edabe80, __pyx_v_partitioning=0x7fa78edc0880, __pyx_v_file_options=0x7fa78edbc1d0,
__pyx_v_max_partitions=1024, __pyx_v_file_visitor=0x55f7fc753d60 <_Py_NoneStruct>, __pyx_v_existing_data_behavior=0x7fa795966c40,
__pyx_v_max_open_files=1024, __pyx_v_max_rows_per_file=0, __pyx_v_min_rows_per_group=0, __pyx_v_max_rows_per_group=1048576, __pyx_v_create_dir=true)
at /arrow/python/build/temp.linux-x86_64-cpython-38/_dataset.cpp:36322
{code}
> [Python][CI] Timeout in test_dataset.py::test_write_dataset_s3_put_only
> -----------------------------------------------------------------------
>
> Key: ARROW-17853
> URL: https://issues.apache.org/jira/browse/ARROW-17853
> Project: Apache Arrow
> Issue Type: Bug
> Components: Continuous Integration, Python
> Reporter: Antoine Pitrou
> Priority: Blocker
> Fix For: 10.0.0
>
>
> This is very likely caused by the fix in ARROW-17614. It can be seen in multiple CI runs and reproduced locally using Archery.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)