Update dependency score_toolchains_rust to v0.10.0 - #412
Open
eclipse-score-bot wants to merge 1 commit into
Open
Update dependency score_toolchains_rust to v0.10.0#412eclipse-score-bot wants to merge 1 commit into
eclipse-score-bot wants to merge 1 commit into
Conversation
eclipse-score-bot
requested review from
4og,
antonkri,
arkjedrz and
pawelrutkaq
as code owners
July 24, 2026 14:34
|
The created documentation from the pull request is available at: docu-html |
Member
|
@arkjedrz, can you please check why rust coverage is failing? |
eclipse-score-bot
force-pushed
the
renovate/score_toolchains_rust-0.x
branch
from
July 30, 2026 13:34
5a91459 to
16aa6e5
Compare
dcalavrezo-qorix
added a commit
to eclipse-score/toolchains_rust
that referenced
this pull request
Jul 31, 2026
#35) 1.3.0 mixed artifacts from two different builds: the coverage-tools tarball was freshly rebuilt (ubuntu20-prof tree) while the main toolchain tarballs were carried over (ubuntu24-prof tree). The dynamically linked Rust tools (symbol-report/blanket) require the exact libstd of the build that produced them, so every consumer of the default toolchains failed the blanket coverage flow with 'symbol lookup error: undefined symbol: ..._3std...Mutex4wake' (seen on eclipse-score/lifecycle#369 and eclipse-score/baselibs#412). 1.3.1 rebuilds ALL artifacts from a single tree: - symbol-report/blanket ABI-match the shipped libstd again (verified: both carry std build Csi8ZjCaVeSd1) - miri-sysroots now include libprofiler_builtins, so coverage- instrumented compiles against the Miri sysroot no longer fail with E0463 (root fix; the --build_tests_only mitigation in cicd-workflows remains as defense in depth) - QNX toolchains are built with the profiler runtime for the first time - coverage-tools keep llvm-cov/llvm-profdata/llvm-cxxfilt (the 1.3.0 feature enabling Rust coverage instrumentation) Validated against lifecycle with a local override: rust tests green under ferrocene-coverage, blanket report generated (94.25% line coverage), llvm tools and miri profiler_builtins present.
eclipse-score-bot
force-pushed
the
renovate/score_toolchains_rust-0.x
branch
from
July 31, 2026 08:02
16aa6e5 to
a9e210a
Compare
eclipse-score-bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.9.1→0.10.0Release Notes
eclipse-score/toolchains_rust (score_toolchains_rust)
v0.10.0: Ferrocene artifacts updated to ferrocene_toolchain_builder 1.3.1All 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:
Additionally:
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
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.2What's Changed
Full Changelog: eclipse-score/toolchains_rust@v0.9.1...v0.9.2
This PR was generated by #infrastructure automation. Contact us if you have any questions or feedback.