From: Yash Shinde <Yash.Shinde@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Umesh.Kallapa@windriver.com,
Naveen.Gowda@windriver.com, Sundeep.Kokkonda@windriver.com,
Shivaprasad.Moodalappa@windriver.com
Subject: Re: [OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir.
Date: Wed, 24 Jan 2024 12:20:07 +0530 [thread overview]
Message-ID: <0697dfb1-9de8-48d6-aa53-f44cbbdce7df@windriver.com> (raw)
In-Reply-To: <1c7059e4c0bad63e7510f5dafff81bbdfba474e6.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 3414 bytes --]
On 24-01-2024 02:47, 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 Tue, 2024-01-23 at 20:07 +0000, Richard Purdie via
> lists.openembedded.org wrote:
>> On Tue, 2024-01-23 at 05:16 -0800, Shinde, Yash via
>> lists.openembedded.org wrote:
>>> From: Yash Shinde<Yash.Shinde@windriver.com>
>>>
>>> Fixes: Exception: no cargo executable found at
>>> `${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo`
>>>
>>> Fix the cargo binary path error on oe-selftest and path set to rust-snapshot dir.
>>>
>>> Patch sent to upstream-https://github.com/rust-lang/rust/pull/120125
>>>
>>> Signed-off-by: Yash Shinde<Yash.Shinde@windriver.com>
>>> ---
>>> .../rust/files/cargo-path.patch | 37 +++++++++++++++++++
>>> 1 file changed, 37 insertions(+)
>>> create mode 100644 meta/recipes-devtools/rust/files/cargo-path.patch
>> Unlike earlier versions of this series, there were a lot of failures:
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6482
>>
>> Basically every machine except qemumips failed on the toolchain tests.
> I also meant to mention, we need to improve the test output when it
> fails. It is currently near useless :(
The test output log is redirected to '${B}/rustc-1.74.1-src/summary.txt'
file which has
test results and error logs for failed test cases, if any.
I assume you are asking for more details in the cmd window of oe-selftest?
$ oe-selftest -r rust
cmdline output:
/
/
/2024-01-23 20:08:39,227 - oe-selftest - INFO - Changing cwd to
/home/poky/build
2024-01-23 20:08:39,228 - oe-selftest - INFO - Adding layer libraries:
2024-01-23 20:08:39,228 - oe-selftest - INFO - /home/poky/meta/lib
2024-01-23 20:08:39,228 - oe-selftest - INFO - /home/poky/meta-yocto-bsp/lib
2024-01-23 20:08:39,228 - oe-selftest - INFO - /home/poky/meta-selftest/lib
2024-01-23 20:08:39,229 - oe-selftest - INFO - Checking base
configuration is valid/parsable
2024-01-23 20:08:40,757 - oe-selftest - INFO - Adding: "include
selftest.inc" in /home/poky/build-st/conf/local.conf
2024-01-23 20:08:40,757 - oe-selftest - INFO - Adding: "include
bblayers.inc" in bblayers.conf
2024-01-23 20:08:40,758 - oe-selftest - INFO - test_rust
(rust.RustSelfTestSystemEmulated)
2024-01-23 21:22:50,600 - oe-selftest - INFO - ... ok
2024-01-23 21:22:50,622 - oe-selftest - INFO -
----------------------------------------------------------------------
2024-01-23 21:22:50,622 - oe-selftest - INFO - Ran 1 test in 4450.264s
2024-01-23 21:22:50,622 - oe-selftest - INFO - OK
2024-01-23 21:23:08,292 - oe-selftest - INFO - RESULTS:
2024-01-23 21:23:08,292 - oe-selftest - INFO - RESULTS -
rust.RustSelfTestSystemEmulated.test_rust: PASSED (4449.86s)
2024-01-23 21:23:08,477 - oe-selftest - INFO - SUMMARY:
2024-01-23 21:23:08,478 - oe-selftest - INFO - oe-selftest () - Ran 1
test in 4450.264s
2024-01-23 21:23:08,478 - oe-selftest - INFO - oe-selftest - OK - All
required tests passed (successes=1, skipped=0, failures=0, errors=0)
/
Currently, it shows above info which is similar to other toolchain
oe-selftests.
Let me know how the output log should look like?
Regards,
Yash
> Cheers,
>
> Richard
[-- Attachment #2: Type: text/html, Size: 5123 bytes --]
next prev parent reply other threads:[~2024-01-24 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 13:16 [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 2/7] rust: detect user-specified custom targets in compiletest Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 3/7] rust: Enable RUSTC_BOOTSTRAP to use nightly features during rust oe-selftest Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 4/7] rust: Fix assertion failure error on oe-selftest Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 5/7] rust: Add new tests in the exclude list for rust oe-selftest Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 6/7] rust: Remove the test cases whose parent dir is also present in the exclude list Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 7/7] rust: Enable rust oe-selftest Yash.Shinde
2024-01-23 20:07 ` [OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir Richard Purdie
2024-01-24 6:48 ` Yash Shinde
[not found] ` <17AD12BD124D26C8.31068@lists.openembedded.org>
2024-01-23 21:17 ` Richard Purdie
2024-01-24 6:50 ` Yash Shinde [this message]
2024-01-24 10:21 ` Richard Purdie
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=0697dfb1-9de8-48d6-aa53-f44cbbdce7df@windriver.com \
--to=yash.shinde@windriver.com \
--cc=Naveen.Gowda@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=Umesh.Kallapa@windriver.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