From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D run on Renesas board - issue
Date: Fri, 03 Nov 2017 16:04:58 +0000 [thread overview]
Message-ID: <87k1z7nyad.fsf@ctlt579.codethink.co.uk> (raw)
In-Reply-To: <d06c1efd762e425b9fdbc5c263747828@RVC-EX13-M02.rvc.renesas.com> (Binh Thanh. Nguyen's message of "Thu, 2 Nov 2017 10:05:02 +0000")
"Binh Thanh. Nguyen" <binh.nguyen.uw@rvc.renesas.com> writes:
> Hello Daniel, Robert,
>
> We are facing an issue when trying to run healthcheck using B at D on Renesas board.
> I would like to attach the log and the healthcheck script (we modified the healthcheck from Daniel)
>
> The boot action was passed, but after that, look like LAVA cannot send
> command to Board, only send "#" (it supposed to be "uname").
> I wonder if you met same issue before?
> And if possible, please give us any hints you may have for debugging this issue!
>
> Best regards,
> Binh Nguyen
Thanh
Sorry for the delay in responding!
That test is missing a deploy section (all commented out) are you trying
to make the test too minimal? LAVA tends to swallow output if it is what
is expected.
Robert
next prev parent reply other threads:[~2017-11-03 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 10:05 [cip-dev] B@D run on Renesas board - issue Binh Thanh. Nguyen
2017-11-03 16:04 ` Robert Marshall [this message]
2017-11-06 2:18 ` Daniel Sangorrin
2017-11-08 7:26 ` Binh Thanh. Nguyen
2017-11-15 10:21 ` Trung. Huynh
2017-11-15 13:59 ` Robert Marshall
2017-11-16 8:11 ` Daniel Sangorrin
2017-11-16 8:48 ` Trung. Huynh
2017-11-16 8:54 ` Daniel Sangorrin
2017-11-17 9:18 ` Robert Marshall
2017-11-27 10:45 ` Trung. Huynh
2017-11-30 7:53 ` Daniel Sangorrin
2017-11-30 9:09 ` Robert Marshall
2017-11-30 19:42 ` Agustin Benito Bethencourt
2017-12-05 9:09 ` Trung. Huynh
2017-12-11 6:46 ` Daniel Sangorrin
2017-12-11 9:54 ` Trung. Huynh
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=87k1z7nyad.fsf@ctlt579.codethink.co.uk \
--to=robert.marshall@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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