Update dependency score_toolchains_rust to v0.10.0

[eclipse-score-bot]

This PR contains the following updates:

Package	Type	Update	Change
score_toolchains_rust	bazel_dep	minor	0.9.1 → 0.10.0

---

Release Notes

eclipse-score/toolchains_rust (score_toolchains_rust)

v0.10.0: Ferrocene artifacts updated to ferrocene_toolchain_builder 1.3.1

All artifact pins (toolchain tarballs for all four target triples, Miri sysroots, coverage-tools) now point to builder release 1.3.1, which rebuilds all artifacts from a single build tree. This fixes two issues introduced by the mixed-build 1.3.0 artifacts referenced in 0.9.2:

• Fixed: symbol-report/blanket crashed at startup (symbol lookup error: undefined symbol: ..._3std...Mutex4wake, exit 127), breaking the Ferrocene rust-coverage flow for all consumers of the default toolchains (seen on eclipse-score/lifecycle#369, eclipse-score/baselibs#412). The coverage tools are now ABI-consistent with the shipped libstd.
• Fixed: Miri sysroots now include libprofiler_builtins, so crates compiled against the Miri sysroot no longer fail with error[E0463]: can't find crate for 'profiler_builtins' when coverage instrumentation is enabled (e.g. Miri test targets built during bazel coverage runs).

Additionally:

• QNX toolchains are built with the profiler runtime for the first time, laying the groundwork for Rust coverage on QNX targets (includes two compiler-rt portability patches applied in the builder).
• coverage-tools continue to ship llvm-cov/llvm-profdata/llvm-cxxfilt built from the same LLVM as rustc (the 0.9.2 feature enabling Rust coverage instrumentation via rules_rust).

New: examples with CI smoke tests (#​36, fixes #​21)

examples/basic/ demonstrates toolchain consumptione way downstream repositories use it) and runs as asmoke test on every PR: build, test, and a coverage run asserting that real LCOV data is produced. Artifact regressions of the kind
fixed above are now caught in this repository's CI

Upgrade notes

• No MODULE.bazel changes are required in consuminsion and refresh your lockfile (bazel mod deps--lockfile_mode=update).
• All toolchain binaries change with this release ect a full Rust rebuild on first use.
• Reminder from 0.9.2: under bazel coverage, Rust targets are instrumented (-Cinstrument-coverage) because the toolchains declare
  llvm_cov/llvm_profdata. Coverage jobs using wildcald_tests_only so test filters also apply to building (already fixed fleet-wide in eclipse-score/cicd-workflows#164/#​165).

v0.9.2

What's Changed

• aarch64-linux: link libgcc for outline atomic helpers by @​dcalavrezo-qorix in #​32
• ferrocene: wire LLVM coverage tools into generated rust_toolchain by @​dcalavrezo-qorix in #​34

Full Changelog: eclipse-score/toolchains_rust@v0.9.1...v0.9.2

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by #infrastructure automation. Contact us if you have any questions or feedback.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: 5f0283aa-b642-43cf-8c86-d3015560a746
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (29 packages loaded, 10 targets configured)

Analyzing: target //:license-check (86 packages loaded, 10 targets configured)

Analyzing: target //:license-check (142 packages loaded, 384 targets configured)

Analyzing: target //:license-check (157 packages loaded, 3971 targets configured)

Analyzing: target //:license-check (162 packages loaded, 6249 targets configured)

Analyzing: target //:license-check (163 packages loaded, 6261 targets configured)

Analyzing: target //:license-check (167 packages loaded, 6298 targets configured)

Analyzing: target //:license-check (167 packages loaded, 6298 targets configured)

Analyzing: target //:license-check (170 packages loaded, 8185 targets configured)

Analyzing: target //:license-check (173 packages loaded, 11401 targets configured)

Analyzing: target //:license-check (174 packages loaded, 11409 targets configured)

Analyzing: target //:license-check (174 packages loaded, 11409 targets configured)

Analyzing: target //:license-check (174 packages loaded, 11409 targets configured)

INFO: Analyzed target //:license-check (175 packages loaded, 11535 targets configured).
[13 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 32.035s, Critical Path: 2.62s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[github-actions]

The created documentation from the pull request is available at: docu-html

[NicolasFussberger]

Hi @pawelrutkaq, could you take a look at what is the problem updating the rust toolchain?

/home/runner/.bazel/execroot/_main/external/score_toolchains_rust++ferrocene_toolchain_ext+ferrocene_x86_64_unknown_linux_gnu/symbol-report: symbol lookup error: /home/runner/.bazel/execroot/_main/external/score_toolchains_rust++ferrocene_toolchain_ext+ferrocene_x86_64_unknown_linux_gnu/symbol-report: undefined symbol: _RNvMNtNtNtNtCs8TbtzrLADkX_3std3sys4sync5mutex5futexNtB2_5Mutex4wake

and

ERROR: /home/runner/.bazel/external/score_baselibs+/src/log/score_log_fmt/BUILD:15:13: Compiling Rust rlib score_log_fmt (8 files) failed: (Exit 1): process_wrapper failed: error executing Rustc command (from target @@score_baselibs+//src/log/score_log_fmt:score_log_fmt) bazel-out/k8-opt-exec-ST-9c9faeccc416/bin/external/rules_rust+/util/process_wrapper/process_wrapper --subst '***' -- ... (remaining 24 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
error[E0463]: can't find crate for `profiler_builtins`
  |
  = note: the compiler may have been built without the profiler runtime

[dcalavrezo-qorix]

Hi @pawelrutkaq, could you take a look at what is the problem updating the rust toolchain?

/home/runner/.bazel/execroot/_main/external/score_toolchains_rust++ferrocene_toolchain_ext+ferrocene_x86_64_unknown_linux_gnu/symbol-report: symbol lookup error: /home/runner/.bazel/execroot/_main/external/score_toolchains_rust++ferrocene_toolchain_ext+ferrocene_x86_64_unknown_linux_gnu/symbol-report: undefined symbol: _RNvMNtNtNtNtCs8TbtzrLADkX_3std3sys4sync5mutex5futexNtB2_5Mutex4wake

and

ERROR: /home/runner/.bazel/external/score_baselibs+/src/log/score_log_fmt/BUILD:15:13: Compiling Rust rlib score_log_fmt (8 files) failed: (Exit 1): process_wrapper failed: error executing Rustc command (from target @@score_baselibs+//src/log/score_log_fmt:score_log_fmt) bazel-out/k8-opt-exec-ST-9c9faeccc416/bin/external/rules_rust+/util/process_wrapper/process_wrapper --subst '***' -- ... (remaining 24 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
error[E0463]: can't find crate for `profiler_builtins`
  |
  = note: the compiler may have been built without the profiler runtime

@pawelrutkaq @NicolasFussberger

TL;DR: score_toolchains_rust 0.9.2 enables real coverage instrumentation for Rust code. Instrumented Rust compiles need the profiler_builtins crate from the sysroot — but because this repo registers the Miri toolchain in the base platform config, the S-CORE rules_rust fork points all Rust compiles at the Miri sysroot, which does not ship profiler_builtins. Result: E0463 at compile time. Reproduced and diagnosed locally; workaround and root fixes below.

The failure

ERROR: .../score_baselibs+/src/log/score_log_fmt/BUILD:15:13: Compiling Rust rlib score_log_fmt (8 files) failed
error[E0463]: can't find crate for profiler_builtins
= note: the compiler may have been built without the profiler runtime

Why a C++ coverage job compiles Rust at all

The job runs bazel coverage ... --test_lang_filters=-rust,-miri -- //score/.... The filter only controls which tests execute — //score/... still builds every target in the tree, including this repo's Rust libraries (//score/health_monitor/src/rust:health_monitoring_lib, //score/launch_manager/src/alive/src/rust:alive_rs, //score/launch_manager/src/lifecycle_client/src/rust:lifecycle_client_rs) and their score_baselibs Rust dependencies — which is where the compile fails. The build abort is why unrelated C++ tests show NO STATUS.

The causal chain (three interacting pieces)

1. score_toolchains_rust 0.9.2 attaches llvm-cov/llvm-profdata to the Ferrocene toolchains (via the coverage-tools 1.3.0 tarball). This is intentional — it makes rules_rust add --codegen=instrument-coverage under bazel coverage, enabling Rust coverage for S-CORE repos. Before 0.9.2, Rust code was silently never instrumented.
2. Instrumented compiles need the profiler runtime. -Cinstrument-coverage makes rustc auto-inject extern crate profiler_builtins (Rust's wrapper around LLVM compiler-rt's profile runtime — the code that actually writes .profraw). It is resolved from the sysroot at compile time, like std — so even a leaf rlib fails to compile if the sysroot lacks it.
3. The Miri sysroot override. The S-CORE rules_rust fork points every target-side Rust compile at the Miri sysroot whenever a Miri toolchain is resolvable (rustc.bzl: "Point target-side crates at the Miri sysroot so their metadata and std linkage match what the direct miri driver will interpret later"). This repo registers the Miri toolchain in the base configs (.bazelrc:66,75 — build:x86_64-linux / build:arm64-linux), so the override applies to coverage builds too. The Miri sysroot tarball was built without the profiler runtime → E0463.

Evidence (local repro with the exact CI invocation)

The failing rustc command mixes the regular toolchain with the Miri sysroot:

.../ferrocene_x86_64_unknown_linux_gnu/rust_ferrocene/bin/rustc
'--codegen=instrument-coverage'
'--sysroot=external/score_toolchains_rust++ferrocene_toolchain_ext+ferrocene_x86_64_unknown_linux_gnu/miri-sysroot'

'--codegen=instrument-coverage'
'--sysroot=external/score_toolchains_rust++ferrocene_toolchain_ext+ferrocene_x86_64_unknown_linux_gnu/miri-sysroot'

and that sysroot contains libstd-.rlib but no libprofiler_builtins-.rlib (the main toolchain tarballs got the profiler runtime in the ferrocene_toolchain_builder "prof" rebuild in June; the miri-sysroot tarballs never did).

Repos that register Miri only inside dedicated configs (e.g. communication, persistency coverage setups) are unaffected — no sysroot override in their coverage builds.

Workaround to unblock this PR (repo-side, small)

Move the Miri toolchain registration out of the base platform configs into a dedicated config used only by Miri invocations:

.bazelrc — remove from build:x86_64-linux / build:arm64-linux:

--extra_toolchains=@score_toolchains_rust//toolchains/ferrocene:ferrocene_x86_64_unknown_linux_gnu_miri

--extra_toolchains=@score_toolchains_rust//toolchains/ferrocene:ferrocene_aarch64_unknown_linux_gnu_miri

build:miri --config=x86_64-linux
build:miri --extra_toolchains=@score_toolchains_rust//toolchains/ferrocene:ferrocene_x86_64_unknown_linux_gnu_miri

(and invoke Miri tests with --config=miri). Beyond fixing this failure, it restores a healthy invariant: coverage (native instrumentation) and Miri (MIR interpretation for UB detection) are contradictory build modes and should never share a configuration.

Root fixes (tracked separately — either makes the workaround unnecessary)

1. rules_rust fork: gate the Miri sysroot override on actually building for Miri (a build setting/config), not on "a Miri toolchain is registered". Registering a toolchain should not change the semantics of builds that don't use it — this is the class-of-bug fix.
2. ferrocene_toolchain_builder: ship libprofiler_builtins in the miri-sysroot tarballs (same "prof" treatment the main toolchain tarballs received in June), making the two sysroots interchangeable under coverage.