kou commented on PR #37787: URL: https://github.com/apache/arrow/pull/37787#issuecomment-1732792804
> @kou I've rebased to the latest commit ([772a01c](https://github.com/apache/arrow/commit/772a01c080ad57eb11e9323f5347472b769d45de)), but the CI ran into another issue (https://github.com/apache/arrow/actions/runs/6290902281/job/17078761957?pr=37787), which seems to be related with LLVM 17 (#37834)? Do I have to fix that or is there any specific commit I should rebase onto? Oh. We can ignore the failures. We can work on it in a separated PR. > > Could you check the failure on AppVeyor? > > https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/48091110#L2859 > > Do you know what the `AppVeyor` check in CI is? Because I cannot reproduce this issue locally (A M1 MacBook), and several CI checks passed as well. I would like to know what the `AppVeyor` check in CI is and how it is different compared to other C++ checks in CI to see if I can figure out why they failed in that environment. Thanks AppVeyor uses Windows and Visual C++. The failure may be related to Windows and/or Visual C++. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
