Skip to content

fix(tests): qualify importer types in unity builds - #4

Merged
aunjgr merged 1 commit into
matrixorigin:feature/26155-substrait-anti-joinsfrom
aunjgr:fix/28968-importer-unity-tests
Oct 8, 2026
Merged

aunjgr merged 1 commit into
matrixorigin:feature/26155-substrait-anti-joinsfrom
aunjgr:fix/28968-importer-unity-tests

Conversation

@aunjgr

@aunjgr aunjgr commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

The C unit-test unity build imports both std and duckdb from neighboring test sources. This makes the new extension-import test's unqualified pointer and vector names ambiguous and fails compilation in #3.

Qualify the DuckDB types explicitly. Existing test scenarios and assertions are preserved; production importer behavior is unchanged.

Validation: reproduced the original failure using the five-source unity translation unit with Sirius's pinned DuckDB and frozen mo Pixi toolchain, then verified the fixed unity unit compiles. The linked independent C++ consumer passes all 60 assertions. git diff --check passes. macOS CI remains a separate check.

Targets the compatible feature/26155-substrait-anti-joins branch, merged #3 at dd4cab14b82754ca919633913436cd530f496e00. Refs matrixorigin/matrixone#28968 and matrixorigin/matrixone#28966.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant