Skip to content

Update dependency score_toolchains_rust to v0.10.0 - #171

Open
eclipse-score-bot wants to merge 1 commit into
mainfrom
renovate/score_toolchains_rust-0.x
Open

Update dependency score_toolchains_rust to v0.10.0#171
eclipse-score-bot wants to merge 1 commit into
mainfrom
renovate/score_toolchains_rust-0.x

Conversation

@eclipse-score-bot

@eclipse-score-bot eclipse-score-bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
score_toolchains_rust bazel_dep minor 0.8.00.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

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

v0.9.1

What's Changed

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

v0.9.0

What's Changed

Full Changelog: eclipse-score/toolchains_rust@v0.8.0...v0.9.0


  • 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

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown

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: a1823f86-5ef2-4cb6-908c-e3285c204970
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'score_process', the root module requires module version score_process@1.5.4, but got score_process@1.6.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_crates', the root module requires module version score_crates@0.0.9, but got score_crates@0.0.10 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 4 packages loaded
Loading: 4 packages loaded
    currently loading: 
Loading: 4 packages loaded
    currently loading: 
Loading: 4 packages loaded
    currently loading: 
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
INFO: Elapsed time: 11.903s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from 7814eb4 to bf576f8 Compare June 30, 2026 09:56
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from bf576f8 to 5a1f8b5 Compare July 1, 2026 13:49
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from 5a1f8b5 to cfa235c Compare July 3, 2026 10:55
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from cfa235c to cc6530e Compare July 3, 2026 14:47
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from cc6530e to fc6c438 Compare July 7, 2026 12:48
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from fc6c438 to 1734e2b Compare July 8, 2026 14:50
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from 1734e2b to f0f0a34 Compare July 9, 2026 07:11
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from f0f0a34 to 4a052bb Compare July 10, 2026 09:05
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from 4a052bb to ae3ba7b Compare July 22, 2026 10:45
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from ae3ba7b to d527129 Compare July 24, 2026 13:33
@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_toolchains_rust to v0.9.1 Update dependency score_toolchains_rust to v0.9.2 Jul 24, 2026
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from d527129 to cbbfafe Compare July 24, 2026 14:37
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from cbbfafe to 14e00f3 Compare July 28, 2026 17:33
@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_toolchains_rust to v0.9.2 Update dependency score_toolchains_rust to v0.10.0 Jul 31, 2026
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_toolchains_rust-0.x branch from 14e00f3 to 86a6439 Compare July 31, 2026 08:05
@rmaddikery
rmaddikery force-pushed the renovate/score_toolchains_rust-0.x branch from 86a6439 to d7e0687 Compare August 4, 2026 08:22
@rmaddikery
rmaddikery force-pushed the renovate/score_toolchains_rust-0.x branch from d7e0687 to 5737a81 Compare August 4, 2026 08:35
@eclipse-score-bot

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@rmaddikery
rmaddikery force-pushed the renovate/score_toolchains_rust-0.x branch from 5737a81 to 1b452ee Compare August 4, 2026 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants