Alexandre Abadie
Alexandre Abadie
Any progress @Citrullin ?
> What kind of test or tests you think about? I think that running `./dist/tools/compile_and_test_for_board/compile_and_test_for_board.py . --with-test-only --jobs=4` would be useful but will take some time (a couple of hours...
This seems to almost pass the CI now but I don't understand the Rust failure: `riot_wrappers.0bcd1c26-cgu.11:(.text.rust_begin_unwind+0xc): undefined reference to `llvm_asm_is_not_supported_any_more'`. Any idea @chrysn ?
> I could run these tests at other boards - are you interested? That would be nice > Should I first install all remaining software? You can use `BUILD_IN_DOCKER=1` and...
@chrysn, any idea about [this Rust related failure](https://ci.riot-os.org/RIOT-OS/RIOT/18056/c35546d48112d5775496bc04f24b6f4498a4fff8/output/compile/examples/rust-gcoap/cc1352p-launchpad:gnu.txt) reported by Murdock ? `riot_wrappers.0bcd1c26-cgu.11:(.text.rust_begin_unwind+0xc): undefined reference to llvm_asm_is_not_supported_any_more'`
Thanks for the answer @chrysn. This PR is still RFC so not really urgent for now on the actual RIOT code base are quite minimal (mostly code removal and minimal...
@chrysn what is the situation on the Rust side regarding this PR ?
Awesome, it's all green! ... but took 3h23m...
> Even #18208 took 3 hours Well it took exactly 2h47m, it's still 36 minutes less. So this PR adds ~20% total CPU time, it's a lot TBH.
> I strongly push the `HAVE_*` because I think having a verbose (and machine readable) description of the board is a good thing. I have no objection with the `HAVE_`...