kyle/tines
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
143 Commits 1 Branch 1 Tag
v1.0.0
Commit Graph
7 Commits
Author SHA1 Message Date
kyleandClaude Opus 5.5 749d6f54ce ci(fuzz): run cargo-fuzz on nightly and keep crash reproducers 
rust-toolchain.toml overrides `rustup default nightly`, so the scheduled
job ran cargo-fuzz on stable and its -Z flags failed (B7). Every cargo
call now names +nightly. Also:

- upload fuzz/artifacts/node/ when the run fails;
- drop the false claim that the corpus "grows in place across
  schedules": new inputs live only in a 7-day artifact until someone
  minimises and commits them;
- pin actions by SHA as ci.yml does (checkout v4.4.0, upload-artifact
  v4.6.2), and install cargo-fuzz with --locked.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-22 08:44:09 -07:00
kyleandClaude Opus 5.5 7a31edd6ad ci: build tines-core on MSRV instead of testing it 
The msrv job ran `cargo test` on 1.82, which can't parse a proptest
dev-dependency that needs edition 2024 (B5). The MSRV promise covers
building tines-core, so the job now builds it on 1.82 with default
features, with --no-default-features, and for thumbv7em-none-eabihf.
`cargo +1.82.0` makes the toolchain explicit over rust-toolchain.toml.
All three builds pass locally on 1.82.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-22 08:44:09 -07:00
kyle 164cf97a5b test(core): fuzz harness and proptest twin 2026-10-22 08:44:09 -07:00
kyle a43a4966e1 test(core): pinned vectors + MSRV gate 2026-10-22 08:44:09 -07:00
kyle 9d4ed7db24 fix(ci): install libdbus-1-dev for tines-bt's bluer
CI / ci (push) Successful in 1m10s
Details 
The workspace build pulls in bluer -> dbus -> libdbus-sys, which links
against the system D-Bus library. The ubuntu-latest runner has pkg-config
but not dbus-1.pc, so libdbus-sys's build script fails. Install the
libdbus-1-dev headers (matching Dockerfile.ros2) before running the gate.
 2026-10-20 09:47:55 -07:00
kyleandClaude Opus 5.5 111a40236d ci: test the no-alloc build and harden the workflow 
Run clippy, docs and tests for tines-core with --no-default-features,
gating the MemStore-based tests on `alloc` so they compile there. Fail on
rustdoc warnings, pass --locked everywhere, and pin the toolchain to
1.99.0. In the workflow, use read-only permissions, cancel superseded
runs, add a 20-minute timeout, and pin actions to commit SHAs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-18 05:07:12 -07:00
kyle 6907f000a2 ci: add GitHub Actions workflow
CI / ci (push) Successful in 2m10s
Details
2026-10-18 04:30:00 -07:00