Skip to content

Validate chdb-core main artifacts in Rust CI - #64

Open
ShawnChen-Sirius wants to merge 1 commit into
mainfrom
codex/chdb-core-26.9.2-rc.2
Open

ShawnChen-Sirius wants to merge 1 commit into
mainfrom
codex/chdb-core-26.9.2-rc.2

Conversation

@ShawnChen-Sirius

@ShawnChen-Sirius ShawnChen-Sirius commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Run the Rust dynamic and static test matrix against four chdb-core CI artifacts from main commit dec391dcdf788cbecede338a0f305b399d8495e1. Add a static host-backtrace/panic regression for #53 and support the new native archive layouts. This is pre-release validation only; it does not publish a crate or change the engine pin.

Note

Add Rust CI workflow to validate chdb-core main artifacts

  • Adds a pull-request workflow that verifies chdb-core main artifacts by pinned SHA, downloads them, and runs dynamic and static Rust builds and tests across a four-OS/arch matrix (Linux, macOS, plus durable and durable-s3 coverage) in core-main-artifact-check.yml
  • Rewrites bundled_runtime_symbols_cannot_bind_host to accept the supported archive layouts: prelinked Linux archives and macOS archives with renamed private runtime symbols, while still rejecting unknown layouts
  • Adds a static-only host_backtrace_and_panic test case that disables engine signal handlers, forces a failing query, and checks the host Rust backtrace and a catchable panic in runtime_faces.rs
  • Behavioral Change: the workflow job fails when the pinned chdb-core run does not match the expected SHA, successful main-branch conclusion, or expected artifact contents; the static archive test no longer fails on valid prelinked Linux archives

Macroscope summarized 6acf0f3.

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