($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Alex Kiernan <alex.kiernan@gmail.com>
To: "Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>,
	 Randy MacLeod <randy.macleod@windriver.com>,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Debugging rust oe-selftest failures
Date: Wed, 3 Apr 2024 12:20:59 +0000	[thread overview]
Message-ID: <CAO5Uq5Q4f4Q+3yR6JZcxhXOP_mpmyzJ0yYtO5SO1_6ZOwdHEzw@mail.gmail.com> (raw)

Hi Sundeep (or anyone else with insight on this!)

How do you go about debugging rust oe-selftest failures? I've bumped
everything up to 1.77 (https://github.com/akiernan/poky) but
oe-selftest fails for reasons that aren't immediately obvious to me...

https://gist.github.com/akiernan/6cc6131c1ec3af866098a9318679cf1b

Any clues?

-- 
Alex Kiernan


             reply	other threads:[~2024-04-03 12:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 12:20 Alex Kiernan [this message]
2024-04-04  9:07 ` Debugging rust oe-selftest failures Yash Shinde
2024-04-05 11:28   ` [OE-core] " Alex Kiernan
2024-05-14 15:52     ` Randy MacLeod
2024-05-16  9:19       ` Alexander Kanavin
2024-05-16 10:15         ` Richard Purdie
2024-05-16 10:23           ` Alexander Kanavin
2024-05-16 10:56             ` Yash Shinde
2024-05-16 11:00               ` Alexander Kanavin
     [not found]               ` <17CFF314D55865EC.16299@lists.openembedded.org>
2024-05-16 11:29                 ` Alexander Kanavin
2024-05-19 14:45                   ` Yash Shinde
2024-05-21 12:50                     ` Alexander Kanavin
2024-05-23 14:16                       ` Yash Shinde
2024-05-23 14:22                         ` Alexander Kanavin
2024-05-24 12:52                           ` Yash Shinde
     [not found]                     ` <17D181FFD1A7EBE8.4453@lists.openembedded.org>
2024-05-21 12:52                       ` 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=CAO5Uq5Q4f4Q+3yR6JZcxhXOP_mpmyzJ0yYtO5SO1_6ZOwdHEzw@mail.gmail.com \
    --to=alex.kiernan@gmail.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).