public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Marek Vasut <marex@denx.de>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [PATCH v2] pytest: Show a message when sandbox crashes
Date: Fri, 15 Oct 2021 07:52:39 -0400	[thread overview]
Message-ID: <20211015115239.GV7964@bill-the-cat> (raw)
In-Reply-To: <20211008151523.3283426-1-sjg@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

On Fri, Oct 08, 2021 at 09:15:23AM -0600, Simon Glass wrote:

> When a test hands on a real board there is no way on the console to obtain
> any information about why it hung.
> 
> With sandbox we can actually find out that it died and get a signal or
> exit code. Add this to make it easier to figure out what happened.
> 
> So instead of:
> 
> test/py/u_boot_spawn.py:171: in expect
>     c = os.read(self.fd, 1024).decode(errors='replace')
> E   OSError: [Errno 5] Input/output error
> 
> We get:
> 
> test/py/u_boot_spawn.py:171: in expect
>     c = os.read(self.fd, 1024).decode(errors='replace')
> E   ValueError: U-Boot exited with signal 11 (Signals.SIGSEGV)
> 
> Signed-off-by: Simon Glass <sjg@chromium.org>

Applied to u-boot/master, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2021-10-15 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 15:15 [PATCH v2] pytest: Show a message when sandbox crashes Simon Glass
2021-10-15 11:52 ` Tom Rini [this message]

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=20211015115239.GV7964@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=marex@denx.de \
    --cc=sjg@chromium.org \
    --cc=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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