We currently lack CI coverage for embedded platforms. Current CI --all-features checks do not compile code gated on embedded targets, so embedded-only API or compile regressions can pass CI unnoticed. For example, the embedded-svc-http transport is only compiled when target_os = "espidf".
Add a CI job that checks at least one ESP-IDF target, for example riscv32imc-esp-espidf with --no-default-features --features embedded-svc-http. A local validation command that worked was:
MCU=esp32c3 cargo +nightly check -Zbuild-std=std,panic_abort -p sentry --target riscv32imc-esp-espidf --no-default-features --features embedded-svc-http
The job will likely need ESP-IDF/Rust setup via espup, rust-src, and build-std support. If a full ESP-IDF install is too slow for regular PR CI, consider weekly CI or a reduced check that still compiles embedded-target code.
We currently lack CI coverage for embedded platforms. Current CI
--all-featureschecks do not compile code gated on embedded targets, so embedded-only API or compile regressions can pass CI unnoticed. For example, theembedded-svc-httptransport is only compiled whentarget_os = "espidf".Add a CI job that checks at least one ESP-IDF target, for example
riscv32imc-esp-espidfwith--no-default-features --features embedded-svc-http. A local validation command that worked was:The job will likely need ESP-IDF/Rust setup via
espup,rust-src, andbuild-stdsupport. If a full ESP-IDF install is too slow for regular PR CI, consider weekly CI or a reduced check that still compiles embedded-target code.