kou commented on PR #13244: URL: https://github.com/apache/arrow/pull/13244#issuecomment-1149329327
Thanks for the note. It takes 3 hours but finished: https://github.com/ursacomputing/crossbow/runs/6768731699?check_suite_focus=true Test was failed: ```text C:\>python -c "import pyarrow.fs" || exit /B 1 Fatal error condition occurred in C:\vcpkg\buildtrees\aws-c-io\src\9e6648842a-364b708815.clean\source\event_loop.c:74: aws_thread_launch(&cleanup_thread, s_event_loop_destroy_async_thread_fn, el_group, &thread_options) == AWS_OP_SUCCESS Exiting Application at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE6ADB1BA0: execute_onexit_table at 0x7FFE6ADB1BA0: execute_onexit_table at 0x7FFE6ADB1BA0: execute_onexit_table at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE61AE80D0: arrow::fs::S3FileSystem::region at 0x7FFE9D775AA0: RtlAnsiStringToUnicodeString at 0x7FFE9D7790F0: LdrShutdownProcess at 0x7FFE9D7BCAB0: RtlExitUserProcess at 0x7FFE6B6FD620: ExitProcess at 0x7FFE6ADC0C50: exit at 0x7FFE6ADC0C50: exit at 0x00007FF7F80E1297: Failed to lookup symbol: error 487 at 0x7FFE6B6F7960: BaseThreadInitThunk at 0x7FFE9D7AA2D0: RtlUserThreadStart ``` > I doubt that the next run after a push will properly have a cache hit (which is a docker/compose issue) Can we try this without merging by removing `{% if arrow.branch == 'master' %}` https://github.com/apache/arrow/pull/13244/files#diff-25c537a1e95363191925a41a3778934a245f8fa8be4d9472b5edefe87d2d8f41R69 ? -- 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]
