All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bird, Timothy" <Tim.Bird@sony.com>
To: "dhinakar.k@samsung.com" <dhinakar.k@samsung.com>,
	"fuego@lists.linuxfoundation.org"
	<fuego@lists.linuxfoundation.org>
Cc: Frank Rowand <frowand.list@gmail.com>
Subject: Re: [Fuego] Functional.fuego_board_check test failure - console log (/dev/ttyUSB0)
Date: Thu, 27 Apr 2017 16:49:28 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF1FA85973@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <20170427043427epcms5p15f3469b5220306d09c4e061ee73735cb@epcms5p1>



> -----Original Message-----
> From: Dhinakar Kalyanasundaram on Wednesday, April 26, 2017 9:34 PM
> 
> Thanks Tim for reproducing the issue.
> 
> I will check with the development manager regarding using 'bash' on the
> target.

Note that I'm pretty sure dash would work also.

Can't you just build bash or dash and put it on the target yourself?
sercp seems to work, and you only need to do this once.  It doesn't
have the be the main shell of the target, just installed somewhere
it can be used.  the sequence would be:
Once:
 * build bash or dash for the target (or find an ARM version somewhere on the Internet)
 * install it on target (somewhere like /usr/local/bin)

Once before executing tests:
 * manually start /usr/local/bin/bash on target so it will be the console shell

During tests:
 * run tests normally, and they should use that shell.

After executing tests:
 * just exit the shell on the console, to return to the original busybox shell.

Eventually, invoking the alternate shell could be put into something like 
the ov_transport_connect() function (when that is created).  But it could
be done manually as a workaround for the short term.
> 
> Meanwhile, Is it difficult to fix this issue or any workaround available?

Well, this should get fixed in serio - it should handle busybox sh correctly.
I don't have time to work on this much this week, though.  I don't have any
workaround aside from using a supported shell.

 -- Tim


  reply	other threads:[~2017-04-27 16:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170419130549epcms5p594b87b8ae8e265e644f9f60ae5d7d80d@epcms5p5>
     [not found] ` <20170419125909epcms5p6ae6c34804cd8eab710cf4dbd80692188@epcms5p6>
     [not found]   ` <CGME20170419125909epcms5p6ae6c34804cd8eab710cf4dbd80692188@epcms5p2>
2017-04-19 13:31     ` [Fuego] Functional.fuego_board_check test failure queries (/dev/ttyUSB0) Dhinakar Kalyanasundaram
     [not found]   ` <CGME20170419125909epcms5p6ae6c34804cd8eab710cf4dbd80692188@epcms5p8>
2017-04-19 13:29     ` [Fuego] Functional.fuego_board_check test failure - console log (/dev/ttyUSB0) Dhinakar Kalyanasundaram
2017-04-25 21:45       ` Bird, Timothy
     [not found]       ` <CGME20170419125909epcms5p6ae6c34804cd8eab710cf4dbd80692188@epcms5p6>
2017-04-26 17:58         ` Dhinakar Kalyanasundaram
2017-04-26 18:35           ` Bird, Timothy
2017-04-27  1:13           ` Bird, Timothy
     [not found]           ` <CGME20170419125909epcms5p6ae6c34804cd8eab710cf4dbd80692188@epcms5p1>
2017-04-27  4:17             ` Dhinakar Kalyanasundaram
2017-04-27  4:34             ` Dhinakar Kalyanasundaram
2017-04-27 16:49               ` Bird, Timothy [this message]
2017-05-17 11:31             ` [Fuego] Setup Build Trigger based on Git/Gerrirt events Dhinakar Kalyanasundaram
2017-05-05  8:36         ` Dhinakar Kalyanasundaram
2017-05-12  5:23           ` Bird, Timothy
2017-05-03 12:35     ` [Fuego] Functional.fuego_board_check test failure - console log (/dev/ttyUSB0) Dhinakar Kalyanasundaram
2017-05-03 17:06       ` Bird, Timothy
     [not found]       ` <CGME20170419125909epcms5p6ae6c34804cd8eab710cf4dbd80692188@epcms5p4>
2017-05-04  3:34         ` Dhinakar Kalyanasundaram
2017-05-05 18:11 Bird, Timothy
     [not found] ` <CGME20170505181150epcas3p148ba4fc7113cc70e7a21473ca34f2930@epcms5p5>
2017-05-11  9:35   ` Dhinakar Kalyanasundaram
2017-05-12  5:04     ` Bird, Timothy

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=ECADFF3FD767C149AD96A924E7EA6EAF1FA85973@USCULXMSG01.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=dhinakar.k@samsung.com \
    --cc=frowand.list@gmail.com \
    --cc=fuego@lists.linuxfoundation.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 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.