Alb3e3 commented on PR #51027:
URL: https://github.com/apache/arrow/pull/51027#issuecomment-5482871643

   The two failures on the previous head split cleanly:
   
   - `AMD64 Conda C++ AVX2` was the same unrelated filesystem lane 
(`arrow-filesystem-test` / `arrow-s3fs-module-test`)
   - `AMD64 Conda Integration Test` exposed a real follow-up in the C Data 
export path for union-backed extensions
   
   Root cause was `cpp/src/arrow/c/bridge.cc` deciding whether to drop the 
leading validity slot from the logical `EXTENSION` type instead of the physical 
storage type. That exported legacy-style extra buffers for union-backed 
extensions (`3` instead of `2` for dense, `2` instead of `1` for sparse), which 
C++ import tolerated but Java/.NET/nanoarrow/Rust rejected.
   
   I pushed `b2b42d4` to switch that export decision to the storage layout and 
added a focused regression in `arrow-c-bridge-test` covering dense + sparse 
union extension exports. Local red/green on that test is now:
   
   - red on old code with the buffer-count mismatch above
   - green after the fix with `arrow-c-bridge-test 
--gtest_filter='TestArrayExport.Extension'`
   
   CI has restarted from the new head.


-- 
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]

Reply via email to