rerun-sdk: Add versions 0.37.2, 0.38.0, 0.38.1 - #2037
Merged
Merged
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The nightly-upgrade PR added these versions to docs/packages/rerun-sdk.yaml without the patches/rerun-sdk/<version>/ directories the workflow reads them from, so every build failed immediately with "No such file or directory" on 0001-lance-core-riscv64-simd-fallback.patch. 0.37.2 pins lance-core/lance-linalg 9.0.0, same as 0.37.1, so its patches are copied unchanged. 0.38.0 and 0.38.1 pin lance 10.0.0; the SIMD source files patches 0001/0003 touch are byte-identical to 9.0.0 (only Cargo.toml/Cargo.lock version metadata changed upstream), so those two patches are also unchanged, but 0002 (the Cargo.lock/Cargo.toml patch.crates-io wiring) is regenerated against the 10.0.0 checksums and path names. The workflow's vendor step also hardcoded the lance version as 9.0.0; it now reads it out of the checked-out Cargo.lock so it doesn't go stale again the next time rerun bumps its lance dependency.
Contributor
Author
|
0.38.0/0.38.1 CI failed compiling rerun_bindings with rustc aborting
via SIGABRT ("free(): corrupted unsorted chunks") -- a heap-corruption
symptom of running out of memory during the single-codegen-unit thin
LTO link that rerun's workspace Cargo.toml bakes into the standard
`release` profile. 0.37.2 built fine; 0.38.x added several new crates
(re_datafusion, re_hdf5, re_mcap, ...) that pushed the link over what
CARGO_BUILD_JOBS=2 + 10 GB swap alone could hold.
Override CARGO_PROFILE_RELEASE_LTO/CODEGEN_UNITS in CIBW_ENVIRONMENT_LINUX
the way build-polars-runtime.yml does (CLAUDE.md gotcha 141), since the
tuning is on the shared `release` profile name and can't be swapped out
by profile selection the way deltalake's custom profile was.
Upstream moved crates/store/re_importer to crates/data_flow/re_importer between 0.37.2 and 0.38.0, so the hardcoded importer_mcap test-assets path in CIBW_TEST_SOURCES only existed for 0.37.2, failing 0.38.0 and 0.38.1 with "Test source ... does not exist." right after the ~6h release build finished. Resolve the crate's parent dir at runtime so it tracks whichever layout the checked-out tag actually has.
luhenry
force-pushed
the
github-actions/nightly-upgrade/rerun-sdk
branch
from
September 19, 2026 18:29
9f83410 to
c9c2450
Compare
0.38.x's new tests/integration/test_chunk_index.py imports the datafusion Python package at module scope, which has no riscv64 wheel anywhere (same class of gap as test_datafusion_utils.py and test_server.py, already ignored above). Ignore it in CIBW_TEST_COMMAND the same way, fixing 0.38.0 and 0.38.1 (same test suite).
…d_stream.py's datafusion tests
The 9 remaining 0.38.1 test failures (0.38.0 shares the same test suite)
split into two distinct root causes, not one:
- test_lerobot_reader.py (5 tests): FileNotFoundError, not datafusion.
CIBW_TEST_SOURCES only copied importer_mcap's own fixtures
(${RE_IMPORTER_DIR}/src/importer_mcap/tests/assets); the new-in-0.38.x
LeRobot fixtures live at the sibling path
${RE_IMPORTER_DIR}/tests/assets/lerobot and were never added. Add that
path instead of ignoring the file -- it's a missing fixture, not a
missing riscv64 wheel. The path exists (unused) in 0.37.2 too, so this
is a no-op there.
- test_optimized_stream.py (4 of its 8 tests): genuine
ModuleNotFoundError: datafusion, via ChunkStore.reader()'s lazy
`import datafusion` (same missing riscv64 wheel as
test_datafusion_utils.py/test_server.py). Its other 4 tests don't call
`.reader()` and pass, so deselect the 4 failing ones individually
instead of ignoring the whole file -- same pattern already used for
test_multi_stream.py::test_isolated_streams and
test_send_dataframe.py::test_send_dataframe_roundtrip.
Verified by grepping rerun-sdk's own test suite (rerun-io/rerun @ 0.38.1)
for every `.reader(` and `import datafusion` usage: these are the only
two files among the currently-collected tests that reach it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automatically generated by the nightly
check_versions.pyrun.rerun-sdk v0.37.1 -> v0.37.2, v0.38.0, v0.38.1
Every
- version:entry added todocs/packages/rerun-sdk.yamlis built by this PR's ownbuild-rerun-sdk.ymlrun; merging publishes the wheels.