wud-if commented on PR #13412: URL: https://github.com/apache/gluten/pull/13412#issuecomment-6593397072
> Please update velox4j ref and fix the CI problems(flink-test failed). @wud-if - **flink-test now builds and runs the suite**: the original failure was `patchelf: maximum file size exceeded` on the ~260MB libvelox.so — the distro patchelf (el8, 0.12) cannot rewrite it. The workflow now installs the static patchelf 0.17.2 into /usr/local before the build (769551d). Version choice was empirical: 0.18.0 clears the big .so but corrupts the bundled third-party libraries (ldd then fails with "ELF load command address/offset not properly aligned" on liblz4.so.1); 0.17.2 handles both — verified against a real 251MB libvelox.so and the bundled .so set (remove+set-rpath land the RUNPATH, ldd loads cleanly). - **velox4j ref**: the CI clone now points at the merged upstream head bigo-sg/velox4j@13afddf2 (the #67 squash — its velox ref is the merged arithmetic revision), as pushed in 58fb240. - **The 5 remaining errors are not from this PR**: `GlutenStreamTwoInputWatermarkStatusTest` (4 errors: "StreamJoin is not yet migrated to operator-owned keyed state; there is no state handler to initialize") and `NexmarkTest` (1 error: same for "GroupWindowAggregator") — both `NOT_IMPLEMENTED` from velox's `experimental/stateful`, introduced by the stateful key-hash-collision change (#79) that is part of the current upstream velox head this PR's stack builds on. Any arithmetic-containing velox revision contains it (the arithmetic squash sits on top of #79), so the pin cannot avoid it. All arithmetic-expression tests are green in this run: RoundFunctionsTest 4/4, AbsFunctionsTest 3/3, FloorCeilFunctionsTest 4/4, UnaryMinusFunctionsTest 2/2, ArithmeticDualRunSqlTest 4/4, RexCallConverterFactoryTest 8/8 (132 tests total: 0 failures, 5 errors — all the stateful ones above, 5 skipped). -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
