From: <rpaluri@codeaurora.org>
To: <automated-testing@lists.yoctoproject.org>,
<yocto@lists.yoctoproject.org>
Subject: BusyBox pTest failure
Date: Wed, 27 Oct 2021 16:22:09 +0530 [thread overview]
Message-ID: <01f601d7cb20$b3551a90$19ff4fb0$@codeaurora.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
Hi,
We are executing busybox pTests and we see that the test case execution
stops at md5sum test case.
We analyzed and see that the execution gets stuck here
<https://github.com/sailfishos-mirror/busybox/blob/master/testsuite/md5sum.t
ests#L29> at Line no 29.
Below are the relevant code lines:
Line no. 28: text="The quick brown fox jumps over the lazy dog"
Line no. 29: text=`yes "$text" | head -c 9999`
I executed above two lines on my host machine and the I get the shell prompt
back but when executed on target machine, I'm not getting the shell prompt,
it gets stuck.
/usr/lib/busybox/ptest # text="The quick brown fox jumps over the lazy dog"
/usr/lib/busybox/ptest # text=`yes "$text" | head -c 9999`
<<get stuck here indefinitely and I don't get the shell prompt>>
I modified Line no. 29 as below (removed " around $text) and the test case
execution proceeds further with "yes: Broken Pipe" error. With the same
modification, I don't see this error on my host machine though.
Line no. 29: text=`yes $text | head -c 9999`
/usr/lib/busybox/ptest # text="The quick brown fox jumps over the lazy dog"
/usr/lib/busybox/ptest # text=`yes $text | head -c 9999`
yes: Broken pipe
My host machine uses Bash as my default shell where as my target uses
busybox sh as my default shell. Does this make any difference?
Any pointers on this will be appreciated.
Thanks,
Ravi
[-- Attachment #2: Type: text/html, Size: 3986 bytes --]
next reply other threads:[~2021-10-27 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 10:52 rpaluri [this message]
[not found] ` <db2f4384600521faa4aeb18151b343e925038087.camel@linuxfoundation.org>
2021-10-27 21:13 ` [Automated-testing] BusyBox pTest failure Khem Raj
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='01f601d7cb20$b3551a90$19ff4fb0$@codeaurora.org' \
--to=rpaluri@codeaurora.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=yocto@lists.yoctoproject.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.