ci: lint all targets, run interop suites for real, compile benches
- clippy --all-targets plus a clawhdf5-format feature matrix (parallel, lz4, zstd, pcodec, fast-checksum); fix the accumulated lint backlog in test, bench and feature-gated code (no behaviour changes). - Install python3 + h5py/numpy/netCDF4/xarray in the CI container and set CLAWHDF5_REQUIRE_INTEROP=1, which makes a missing interop dependency a test failure. Every h5py/netCDF4 interop test used to skip silently in CI. Run the #[ignore]d writer_h5py_tests suite explicitly. - cargo bench --no-run so benches can't rot; fix bench.rs and memory_bench.rs, which no longer compiled against the current strategy/consolidation APIs. - Optional fuzz smoke run via CLAWHDF5_FUZZ_SECONDS. - CHANGELOG and docs/known-issues.md updated. Co-Authored-By: Claude Fable 5.1 <[email protected]>
This commit is contained in:
co-authored by
Claude Fable 5.1
parent
706189c3ef
commit
bbe1baa208
@@ -1,5 +1,39 @@
|
||||
# Changelog
|
||||
|
||||
## Unreleased
|
||||
|
||||
### Bug Fixes
|
||||
- `clawhdf5-format`: compound datatypes written with **default libver bounds**
|
||||
(datatype message version 1 — what plain `h5py.File(path, 'w')` produces)
|
||||
were mis-parsed. The v1 member layout carries 28 bytes of legacy array
|
||||
fields after the byte offset (the parser skipped 24), and v2 pads member
|
||||
names to 8 bytes and has no array fields at all (the parser did neither), so
|
||||
every member after the first byte offset was read from the wrong position —
|
||||
typically surfacing as `Overflow("compound member ...")` on read. Found by
|
||||
adding a default-libver axis to the h5py interop tests; byte-level regression
|
||||
tests for v1 and v2 added.
|
||||
- `clawhdf5-gpu`: `gpu_tests` could hang forever under the default parallel
|
||||
test runner — every test created its own wgpu instance and device at once.
|
||||
Tests now serialise GPU access, and GPU→CPU readback waits are bounded
|
||||
(30 s) so a wedged driver returns `GpuError::BufferMap` instead of blocking.
|
||||
- `clawhdf5-agent`: `benches/bench.rs` and `benches/memory_bench.rs` no longer
|
||||
compiled against the current `strategy`/`consolidation` APIs.
|
||||
|
||||
### CI / Testing
|
||||
- CI now lints every target (`cargo clippy --all-targets`) plus
|
||||
`clawhdf5-format`'s optional features, compiles all benches, and tests the
|
||||
format feature matrix. Previously test/bench code and feature-gated modules
|
||||
were never linted; the accumulated clippy backlog is fixed.
|
||||
- CI installs python3 + h5py/numpy/netCDF4/xarray and sets
|
||||
`CLAWHDF5_REQUIRE_INTEROP=1`, which turns a missing interop dependency into a
|
||||
test **failure**. Until now every h5py/netCDF4 interop test silently skipped
|
||||
in CI, which is how the HDF5 2.0 compound bug fixed in v2.2.0 reached a user.
|
||||
The `#[ignore]`d `writer_h5py_tests` suite is run explicitly.
|
||||
- h5py-generated-file tests now cover default libver bounds as well as
|
||||
`libver='latest'` (HDF5 2.0 raised the default low bound to 1.8).
|
||||
- Optional fuzz smoke run (`CLAWHDF5_FUZZ_SECONDS=N scripts/ci-test.sh`); new
|
||||
datatype corpus seeds for v1 compound and native complex messages.
|
||||
|
||||
## v2.2.0 (2026-09-18)
|
||||
|
||||
### Security
|
||||
|
||||
Reference in New Issue
Block a user