All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: Yash.Shinde@windriver.com,
	openembedded-core@lists.openembedded.org,
	Tim Orling <tim.orling@konsulko.com>,
	Umesh.Kallapa@windriver.com, Naveen.Gowda@windriver.com,
	Sundeep.Kokkonda@windriver.com,
	Shivaprasad.Moodalappa@windriver.com
Subject: Re: [PATCH 2/2] rust: Disable rust oe-selftest
Date: Fri, 8 Dec 2023 15:46:41 +0100	[thread overview]
Message-ID: <2023120814464190b6f0e7@mail.local> (raw)
In-Reply-To: <bb8e3b3c-9f8d-41ac-b67c-f58465c81aef@windriver.com>

On 08/12/2023 09:05:51-0500, Randy MacLeod wrote:
> On 2023-12-08 5:48 a.m., Yash.Shinde@windriver.com wrote:
> > From: Yash Shinde<Yash.Shinde@windriver.com>
> > 
> > After rust is upgraded to 1.71 and later versions, the rust oe-selftest gives
> > build errors due to unstable nightly options(see the error mentioned below). Thus, disable the test suite
> > until the issue is fixed
> > 
> > error: the option `Z` is only accepted on the nightly compiler
> > thread 'main' panicked at 'failed to gather the target spec for x86_64-poky-linux-gnu', synthetic_targets.rs:66:9
> > 
> > Following issues are created in Yocto bugzilla and rust upstream to track this issue-
> > 
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=15275
> > https://github.com/rust-lang/rust/issues/115642
> > https://users.rust-lang.org/t/does-rust-test-suite-supports-nightly-options-during-bootstrapping-in-rust/103108
> > https://users.rust-lang.org/t/unable-to-read-target-specs-when-rust-1-73-is-bootstrapped-in-yocto-poky/102959
> > 
> > Signed-off-by: Yash Shinde<Yash.Shinde@windriver.com>
> > ---
> >   meta/lib/oeqa/selftest/cases/rust.py | 3 +++
> >   1 file changed, 3 insertions(+)
> > 
> > diff --git a/meta/lib/oeqa/selftest/cases/rust.py b/meta/lib/oeqa/selftest/cases/rust.py
> > index 7d148142fc..6dbc517006 100644
> > --- a/meta/lib/oeqa/selftest/cases/rust.py
> > +++ b/meta/lib/oeqa/selftest/cases/rust.py
> > @@ -39,6 +39,9 @@ def parse_results(filename):
> >   @OETestTag("runqemu")
> >   class RustSelfTestSystemEmulated(OESelftestTestCase, OEPTestResultTestCase):
> >       def test_rust(self, *args, **kwargs):
> > +        # Disable Rust Oe-selftest
> > +        self.skipTest("The Rust Oe-selftest is disabled.")
> > +
> >           # build remote-test-server before image build
> >           recipe = "rust"
> >           start_time = time.time()
> 
> Thanks for the Rust update Yash and it's unfortunate that we haven't
> resolved the problems
> with the test suite. We decided to diskable the tests and do the update
> because some changes
> were blocked waiting for a newer version of Rust according to Tim.
> 
> Yash,
> It would be better to disable (skip) the test suite first so that there
> isn't a commit with the testsuite
> broken.
> 
> Alex, the commits are independent, will you please re-order them before
> merging?

Sure!

> 
> ../Randy
> 
> -- 
> # Randy MacLeod
> # Wind River Linux

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-12-08 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 10:47 [PATCH 1/2] rust: Upgrade 1.70.0 -> 1.73.0 Yash.Shinde
2023-12-08 10:48 ` [PATCH 2/2] rust: Disable rust oe-selftest Yash.Shinde
2023-12-08 14:05   ` Randy MacLeod
2023-12-08 14:46     ` Alexandre Belloni [this message]
2023-12-08 15:13       ` Randy MacLeod
  -- strict thread matches above, loose matches on Subject: below --
2023-12-08  9:54 [PATCH 1/2] rust: Upgrade 1.70.0 -> 1.73.0 Yash.Shinde
2023-12-08  9:54 ` [PATCH 2/2] rust: Disable rust oe-selftest Yash.Shinde

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=2023120814464190b6f0e7@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=Naveen.Gowda@windriver.com \
    --cc=Shivaprasad.Moodalappa@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=Umesh.Kallapa@windriver.com \
    --cc=Yash.Shinde@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=tim.orling@konsulko.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 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.