On 2024-07-04 11:21 a.m., Alexander Kanavin via lists.openembedded.org
wrote:
Hello,
I simply ran two independent builds, each with their own sstate. The
host distro is not relevant, as it's been observed on yocto
autobuilder across many different distros.
I'm not sure why you insist on being able to reproduce the issue, as
you're simply going to get the same build trees as in the tarballs I
provided.
Hi Alex,
That's true, but it's always nicer to be able to reproduce a problem
locally so one can tests fixes properly.
Richard and I suggested that we at least get the distro and list of
packages identified so that Sundeep
could see if he can reproduce the problem independently.
You're right that it's not essential but we're also trying to avoid
putting too much extra
load on the autobuilders and the people who run builds there.
It's a long-standing problem that the Rust updates are done and pass
all local tests only
to fail on one or more of the YP AB systems. We'd like to understand why
that happens
so if you could share the info that Sundeep requested, that may help for
this bug and for
future Rust work as well.
Thanks,
../Randy
Alex
On Thu, 4 Jul 2024 at 17:13, Sundeep KOKKONDA via
lists.openembedded.org
<[email protected]> wrote:
Hi Alex,
What distro you used to reproduce the issue & what pkgs were installed. You
used any shared sstate of Yocto?
With this info I will retry to reproduce the issue on my local machine.
Thanks,
Sundeep K.
--
# Randy MacLeod
# Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201582):
https://lists.openembedded.org/g/openembedded-core/message/201582
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
