From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: pgowda cve <pgowda.cve@gmail.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: "Luca Ceresoli via lists.openembedded.org"
<luca.ceresoli=bootlin.com@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Randy MacLeod <rwmacleod@gmail.com>,
Alexander Kanavin <alex.kanavin@gmail.com>,
Vinay Kumar <vinay.m.engg@gmail.com>
Subject: Re: [OE-core] [PATCH v6] Rust Oe-Selftest implementation
Date: Mon, 06 Jun 2022 09:51:48 +0100 [thread overview]
Message-ID: <a3fa5681be1c935b9137ad5c1a8de1c311d0c346.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALY4986aY-X5V2-fcOU+3bovF=kB9t7Uvrh8b_rcqH-pQE9J-w@mail.gmail.com>
On Fri, 2022-06-03 at 18:37 +0530, pgowda cve wrote:
> Hi Luca,
>
> Regarding the issue
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14818
>
> I ran the Oe-Selftest for Rust as well as completed packages and did
> not come across any issues.
> a@yow-fedora-builder1 build]$ uname -a
> Linux yow-fedora-builder1 5.16.18-200.fc35.x86_64 #1 SMP PREEMPT Mon
> Mar 28 14:10:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
>
> The log of tests can be seen as follows:-
> The command used to run the test was as mentioned in the Bugzilla.
> oe-selftest -a -t machine -t toolchain-system -j 15
>
> test_libatomic: PASSED (113.76s)
> 2022-06-03 08:39:19,084 - oe-selftest - INFO - RESULTS -
> gcc.GccLibGompSelfTestSystemEmulated.test_libgomp: PASSED (637.21s)
> 2022-06-03 08:39:19,084 - oe-selftest - INFO - RESULTS -
> gcc.GccLibItmSelfTestSystemEmulated.test_libitm: PASSED (133.31s)
> 2022-06-03 08:39:19,084 - oe-selftest - INFO - RESULTS -
> gcc.GccLibStdCxxSelfTestSystemEmulated.test_libstdcxx: PASSED
> (2546.63s)
> 2022-06-03 08:39:19,084 - oe-selftest - INFO - RESULTS -
> gcc.GxxCrossSelfTestSystemEmulated.test_cross_gxx: PASSED (744.56s)
> 2022-06-03 08:39:19,084 - oe-selftest - INFO - RESULTS -
> glibc.GlibcSelfTestSystemEmulated.test_glibc: PASSED (1101.43s)
> 2022-06-03 08:39:19,085 - oe-selftest - INFO - RESULTS -
> meta_ide.MetaIDE.test_meta_ide_can_build_cpio_project: PASSED (54.33s)
> 2022-06-03 08:39:19,085 - oe-selftest - INFO - RESULTS -
> meta_ide.MetaIDE.test_meta_ide_can_compile_c_program: PASSED (0.19s)
> 2022-06-03 08:39:19,085 - oe-selftest - INFO - RESULTS -
> meta_ide.MetaIDE.test_meta_ide_had_installed_meta_ide_support: PASSED
> (0.01s)
> 2022-06-03 08:39:19,085 - oe-selftest - INFO - RESULTS -
> runqemu.QemuTest.test_qemu_can_shutdown: PASSED (45.98s)
> 2022-06-03 08:39:19,085 - oe-selftest - INFO - RESULTS -
> rust.RustSelfTestSystemEmulated.test_rust: PASSED (8381.70s)
> 2022-06-03 08:39:19,085 - oe-selftest - INFO - RESULTS -
> gcc.GccLibSspSelfTestSystemEmulated.test_libssp: SKIPPED (3.92s)
> 2022-06-03 08:39:22,336 - oe-selftest - INFO - SUMMARY:
> 2022-06-03 08:39:22,336 - oe-selftest - INFO - oe-selftest () - Ran 16
> tests in 19613.479s
> 2022-06-03 08:39:22,336 - oe-selftest - INFO - oe-selftest - OK - All
> required tests passed (successes=15, skipped=1, failures=0, errors=0)
>
> I also ran the Rust Oe-Selftest individually and did not find any issues.
> Can you please share the environment file so that I can reproduce and
> fix the issue?
There isn't any magic environment we can share here I'm afraid. We
don't know why it happens on some autobuilder workers and not on
others, this is something we need to investigate and fix. This is one
of the challenges of these "intermittent" issues.
The errors seem to relate to zlib so it may be worth looking at whether
host headers influence the rust build and those may be causing some
kind of determinism issue. You may have to build the binaries one a
system with the headers, then run them on a system without for example.
Cheers,
Richard
next prev parent reply other threads:[~2022-06-06 8:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 12:20 [PATCH v5] Rust Oe-Selftest implementation pgowda
2022-05-24 11:53 ` pgowda cve
2022-05-24 20:56 ` [OE-core] " Luca Ceresoli
2022-05-25 4:32 ` [PATCH v6] " pgowda
2022-05-25 7:57 ` [OE-core] " Luca Ceresoli
[not found] ` <16F24A16BC7F056F.12338@lists.openembedded.org>
2022-05-31 13:05 ` Luca Ceresoli
2022-06-03 13:07 ` pgowda cve
2022-06-06 8:51 ` Richard Purdie [this message]
2022-06-29 8:18 ` pgowda cve
2022-06-29 16:19 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2022-08-02 3:53 pgowda.cve
2022-08-02 8:38 ` [OE-core] " Luca Ceresoli
2022-08-02 9:07 ` pgowda cve
2022-08-02 9:52 ` Luca Ceresoli
2022-08-02 12:22 ` pgowda cve
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=a3fa5681be1c935b9137ad5c1a8de1c311d0c346.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=luca.ceresoli=bootlin.com@lists.openembedded.org \
--cc=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=rwmacleod@gmail.com \
--cc=vinay.m.engg@gmail.com \
/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