From: Yash Shinde <Yash.Shinde@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Randy.MacLeod@windriver.com, Naveen.Gowda@windriver.com,
Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH 2/2] rust: Upgrade 1.78.0->1.79.0
Date: Tue, 27 Aug 2024 17:41:05 +0530 [thread overview]
Message-ID: <15bf0cae-b114-4ac7-89d9-3f7df77b41bd@windriver.com> (raw)
In-Reply-To: <bbbe564b9b6191edbe62abd69fa3b337ada2ad4a.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]
On 27-08-2024 16:08, Richard Purdie wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Sun, 2024-08-25 at 10:05 -0700, Yash Shinde via
> lists.openembedded.org wrote:
>> From: Yash Shinde<Yash.Shinde@windriver.com>
>>
>> Update the patch files with rust v1.79.0.
>>
>> Drop the following backported patch which is merged
>> with rust v1.79 upgrade.
>>
>> - cross-targets-backport.patch
>>
>> https://blog.rust-lang.org/2024/06/13/Rust-1.79.0.html
>>
>> Signed-off-by: Yash Shinde<Yash.Shinde@windriver.com>
> It seems mostly ok but we did see:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/9385/steps/13/logs/stdio
>
> in Alexandre's build :(
I am looking into the failure but was unable to reproduce it.
The error log says:
/stdio: ERROR: cargo-native-1.79.0-r0 do_compile: Execution of
'/home/pokybuild/yocto-worker/qemuarm64/build/build/tmp/work/x86_64-linux/cargo-native/1.79.0/temp/run.do_compile.1874995'
failed with exit code 101
stdio: ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-worker/qemuarm64/build/build/tmp/work/x86_64-linux/cargo-native/1.79.0/temp/log.do_compile.1874995
stdio: ERROR: Task
(virtual:native:/home/pokybuild/yocto-worker/qemuarm64/build/meta/recipes-devtools/rust/cargo_1.79.0.bb:do_compile)
failed with exit code '1'
stdio: ERROR: Command . ./oe-init-build-env; bitbake core-image-sato
core-image-sato-sdk core-image-minimal core-image-minimal-dev
core-image-full-cmdline core-image-sato:do_populate_sdk
core-image-minimal:do_populate_sdk_ext
core-image-sato:do_populate_sdk_ext -k failed with exit code 1, see
errors above. (1724719291.3: 11079.3)/
I checked "bitbake cargo -c do_compile",
"core-image-minimal:do_populate_sdk" and core-image-sato:do_populate_sdk
and all passed successfully.
The build cmd has many /core-image minimal and sato/ build cmds.
Could you please help me to point out which of these exactly cause the
issue?
Regards,
Yash
>
> Cheers,
>
> Richard
[-- Attachment #2: Type: text/html, Size: 3512 bytes --]
next prev parent reply other threads:[~2024-08-27 12:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 17:05 [PATCH 1/2] rust: Oe-selftest changes for rust v1.79 Yash.Shinde
2024-08-25 17:05 ` [PATCH 2/2] rust: Upgrade 1.78.0->1.79.0 Yash.Shinde
2024-08-27 10:38 ` [OE-core] " Richard Purdie
2024-08-27 12:11 ` Yash Shinde [this message]
2024-08-27 12:24 ` Alexander Kanavin
2024-08-27 12:40 ` Richard Purdie
2024-08-27 12:47 ` Yash Shinde
2024-08-27 13:22 ` Richard Purdie
2024-08-27 16:23 ` Alexander Kanavin
[not found] ` <17EFA275ACF95534.20373@lists.openembedded.org>
2024-08-27 16:25 ` Alexander Kanavin
[not found] ` <17EFA28FD32C2C48.20373@lists.openembedded.org>
2024-08-27 17:16 ` Alexander Kanavin
2024-08-27 19:51 ` Richard Purdie
2024-08-27 20:38 ` Alexander Kanavin
2024-08-27 20:41 ` Richard Purdie
2024-08-27 20:47 ` Alexander Kanavin
2024-08-27 21:02 ` Khem Raj
2024-08-28 13:11 ` Alexander Kanavin
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=15bf0cae-b114-4ac7-89d9-3f7df77b41bd@windriver.com \
--to=yash.shinde@windriver.com \
--cc=Naveen.Gowda@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox