prmoore77 commented on PR #4634: URL: https://github.com/apache/arrow-adbc/pull/4634#issuecomment-5126337821
Manual verification on Windows-on-ARM done, per the release-verification question above. I took the npm tarballs built by this PR's packaging run (the `node-packages` artifact from [run 30506435560](https://github.com/apache/arrow-adbc/actions/runs/30506435560) — the main `@apache-arrow/adbc-driver-manager` package plus the new `win32-arm64-msvc` platform package) and installed them on a native Windows arm64 VM (Azure, Node.js v24.18.1 arm64). The driver manager then loaded a native win_arm64 ADBC driver ([gizmosql-adbc](https://github.com/gizmodata/gizmosql-adbc) v2.0.4) and ran a query over TLS against a GizmoSQL server **also running natively on the same Windows arm64 box** (DuckDB backend, TPC-H sf=0.1 data loaded): ``` platform: win32 arch: arm64 node: v24.18.1 native addon: ...\node_modules\@apache-arrow\adbc-driver-manager-win32-arm64-msvc\adbc-driver-manager.win32-arm64-msvc.node driver: ...\libadbc_driver_gizmosql-v2.0.4-windows_arm64\libadbc_driver_gizmosql.dll uri: gizmosql://localhost:31337 row: {"one":1,"backend_version":"v1.5.5"} PASS: @apache-arrow/adbc-driver-manager loaded the native arm64 addon and executed a query through libadbc_driver_gizmosql.dll ``` So the CI-built artifacts work end-to-end on Windows arm64: addon load → driver load → TLS connect → query → Arrow results, with every component (Node, addon, driver, server) running natively on arm64. I'm happy to repeat this against the actual release candidates during release verification, I have this VM available all of the time (though it is shut down when I'm not using it for testing). -- 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]
