[ 
https://issues.apache.org/jira/browse/ARROW-14911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475815#comment-17475815
 ] 

Weston Pace commented on ARROW-14911:
-------------------------------------

I'm not sure the input data will be as important.  If I am reading the test 
correctly it initializes a random generator with a fixed seed.  So even though 
the test is testing random data it should be deterministic between runs.  I 
have verified that we are running this test on our CI servers (which includes 
VS2017 although at a higher version than 19.12).

The test does do some parallel execution so there is a possibility it is a race 
condition causing the flakiness.

I also built locally with VS2019 in both debug mode and release and tried 
running this test both with and without CPU stress and have not been able to 
reproduce it.  I was doing this against the latest master and not the 6.0.1 tag 
so that might be a factor.  I will try and reproduce this some more tomorrow 
with VS2017.

[[email protected]] How reliable is this failure?  Does it fail every time or 
intermittently?  When it fails does it always display the exact same output? 
(e.g. {{RIGHT SEMI IS_IS...}})

At the moment I'm not sure this qualifies as a blocker.  

> [C++] arrow-compute-hash-join-node-test failed
> ----------------------------------------------
>
>                 Key: ARROW-14911
>                 URL: https://issues.apache.org/jira/browse/ARROW-14911
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++
>    Affects Versions: 6.0.0, 6.0.1
>            Reporter: Renat Valiullin
>            Assignee: Michal Nowakiewicz
>            Priority: Blocker
>              Labels: query-engine
>             Fix For: 7.0.0
>
>         Attachments: workaround.patch
>
>
> arrow-compute-hash-join-node-test failed in my environment (windows, msvc 
> 19.12.25835)
> because in HashJoinBasicImpl::ProbeBatch_Lookup hash_table_ is empty, but 
> hash_table_empty_ is false. 
> I workaround this issue using the attached patch, but fix likely should be 
> different.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to