Taiki Endo

> ```yml > runs-on: ${{ inputs.platform }} > ``` > ```yml > target: ${{ inputs.target }} > ``` Your workflow is using `inputs.platform` and `inputs.target` to specify platform/target, but some...

> reported that, > ``` > Status: Downloaded newer image for ghcr.io/cross-rs/mipsel-unknown-linux-gnu:0.2.5 That issue is the same issue as the one I mentioned in https://github.com/taiki-e/upload-rust-binary-action/issues/94#issuecomment-2666489330.

> I see, looks like they dont support the allocator, > ``` > Invalid configuration `riscv64gc-unknown-linux-musl': machine `riscv64gc-unknown' not recognized > configure: error: /bin/bash build-aux/config.sub riscv64gc-unknown-linux-musl failed > ``` This...

riscv64gc-unknown-linux-musl jemalloc configure script issue should be addressed in the latest setup-cross-toolchain-action@v1 (https://github.com/taiki-e/setup-cross-toolchain-action/commit/9547f7321b5533797e04789a9fb6602c2554e8ce). The error in s390x-unknown-linux-musl is the same issue as mipsel-unknown-linux-gnu mentioned in https://github.com/taiki-e/upload-rust-binary-action/issues/94#issuecomment-2666590422, which is obvious since...

Oh, it is actually a jemalloc-sys bug and fixed in main branch of them, but not yet released: https://github.com/tikv/jemallocator/commit/b913c24fdd4841bb4028a00207dfeb76832c806b

AFAIK, boxing is to avoid stack overflows. However, I think the boundary should be larger in the release mode like tokio does. https://github.com/tokio-rs/tokio/blob/512e9decfb683d22f4a145459142542caa0894c9/tokio/src/runtime/mod.rs#L400 Another approach that would may work is...

Does `Swatinem/rust-cache` action not work? I think that is what is often used when using cache for Rust on GitHub Actions.

Unfortunately, sharing caches that are not based on the default branch with other branchs/tags does not seem to be supported: https://github.com/actions/cache/blob/main/tips-and-workarounds.md#use-cache-across-feature-branches I guess this issue can be addressed by doing...

This is a compiler bug (or limitation). (Also, even `exit()` is not handled well by compilers on some platforms: https://github.com/rust-lang/rust/issues/77553)

https://github.com/rust-lang/rust/issues/77553 is about `std::process::exit()`, your issue is probably about SIGKILL. `std::process::exit()` works on linux and macos, but SIGKILL probably does not work on any platform.