You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Percy Camilo Triveño Aucahuasi (Jira)" <ji...@apache.org> on 2022/09/28 04:57:00 UTC
[jira] [Commented] (ARROW-17687) [C++] ScanningStress test is flaky in CI
[ https://issues.apache.org/jira/browse/ARROW-17687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610349#comment-17610349 ]
Percy Camilo Triveño Aucahuasi commented on ARROW-17687:
--------------------------------------------------------
I got this [^backtrace.log.cpp].
It seems we are moving the unique_locker and trying to lock some invalid mutex.
Also, I was able to get another issue, this time a deadlock using these values:
constexpr int kNumIters = 1;
constexpr int kNumFragments = 10;
constexpr int kBatchesPerFragment = 10;
constexpr int kNumConcurrentTasks = 2;
I'll try to explore more about where we are getting these errors, so far I was able to reduce and reproduce the test issue using these values:
constexpr int kNumIters = 1;
constexpr int kNumFragments = 2;
constexpr int kBatchesPerFragment = 1;
constexpr int kNumConcurrentTasks = 1;
Given that we can use C++ 17 now, I'll try to use the new std::scoped_lock instead of the the other lockers (in the places where it make sense to do so)
> [C++] ScanningStress test is flaky in CI
> ----------------------------------------
>
> Key: ARROW-17687
> URL: https://issues.apache.org/jira/browse/ARROW-17687
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Reporter: Weston Pace
> Assignee: Percy Camilo Triveño Aucahuasi
> Priority: Major
> Attachments: backtrace.log.cpp
>
>
> There is at least one nightly failure: https://github.com/ursacomputing/crossbow/actions/runs/3033965241/jobs/4882574634
--
This message was sent by Atlassian Jira
(v8.20.10#820010)