All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <alhe@linux.microsoft.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] rust: Avoid passing host-specific information to crates Strict Version Hash
Date: Tue, 25 Aug 2026 20:48:20 +0200	[thread overview]
Message-ID: <DKY8ZEFTEBOF.2QVJI76PJ4GKR@bootlin.com> (raw)
In-Reply-To: <20260824235606.4035992-1-alhe@linux.microsoft.com>

On Tue Aug 25, 2026 at 1:56 AM CEST, Alejandro Hernandez Samaniego via lists.openembedded.org wrote:
> rustc computes each crate's Strict Version Hash (SVH) using inputs that include
> the *stage0/stage1 bootstrap compiler* fingerprint, which in turn depends on the
> build host arch.
>
> This eventually may cause sstate matches across architectures for artifacts that
> are actually different, causing autobuilder intermitent reproducibility issues.
>
> To avoid this, pass a fixed value instead of host-specific bits to the specified
> hash.
>
> [YOCTO #15554]
>
> Assisted-by: AI - OpenAI
> Signed-off-by: Alejandro Hernandez <alhe@linux.microsoft.com>

Hi Alejandro,

This looks broken here:

ERROR: rust-native-1.97.1-r0 do_install: Execution of '/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/x86_64-linux/rust-native/1.97.1/temp/run.do_install.2682640' failed with exit code 1
...
ERROR: Logfile of failure stored in: /srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/x86_64-linux/rust-native/1.97.1/temp/log.do_install.2682640
...
|     Building [==================>      ] 275/348: object, schemars, tracing-s…
|    Compiling rustc_span v0.0.0 (/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work-shared/rust-source-1.97.1-r0/sources/rustc-1.97.1-src/compiler/rustc_span)
|     Building [==================>      ] 276/348: object, schemars, tracing-s…
| error: expected `;`, found `StableCrateId`
|    --> /rustc-dev/8bab26f4f68e0e26f0bb7960be334d5b520ea452/compiler/rustc_span/src/def_id.rs:200:59
|     |
| 200 |         hasher.write(b"

https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4510

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-08-25 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 23:56 [PATCH v2] rust: Avoid passing host-specific information to crates Strict Version Hash Alejandro Hernandez
2026-08-25 18:48 ` Mathieu Dubois-Briand [this message]
2026-08-25 20:13   ` [OE-core] " Alejandro Hernandez
     [not found]   ` <18CF258177A95B06.3360474@lists.openembedded.org>
2026-08-26 15:54     ` Alejandro Hernandez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DKY8ZEFTEBOF.2QVJI76PJ4GKR@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=alhe@linux.microsoft.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.