From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Policy regarding BASH
Date: Thu, 19 Sep 2013 16:50:33 +0400 [thread overview]
Message-ID: <523AF319.50702@oracle.com> (raw)
In-Reply-To: <523AF25C.1010907@oracle.com>
On 09/19/2013 04:47 PM, Stanislav Kholmanskikh wrote:
> Hi!
>
> During looking into shell testcases I came across a situation where
> * main shell script is a bash script (ie it has #!/bin/bash in the header)
> * for each testcase number main shell script executes a separate (child)
> shell-script which has #!/bin/sh in the header
>
> So If I try to run main script on Debian (where /bin/sh points to
> /bin/dash) I get error like this:
> root@debian7-x64:/opt/ltp/testcases/bin# ./run_cpuset_test.sh 3
> TEST 3: CPUSET CONTROLLER TESTING
> TEST STARTED: Please avoid using system while this test executes
> ./cpuset_exclusive_test.sh: 34: ./cpuset_funcs.sh: arithmetic
> expression: expecting primary: "N_NODES++"
>
> So what is the policy regarding bash presence in LTP? Is it permitted to
> write testcases using bash specific features?
> Or are we strongly encouraged to use "common shell" only?
>
> And how should I proceed with this particular testcase? Try to remove
> "bashism" or just change header of child scripts from "#!/bin/sh" to
> "#!/bin/bash"?
>
> Thank you.
The problem is not because child is a "sh" script but because child
includes cpuset_funcs.sh file (main includes it also) but
this file has bash-specific things.
>
>
>
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-09-19 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 12:47 [LTP] Policy regarding BASH Stanislav Kholmanskikh
2013-09-19 12:50 ` Stanislav Kholmanskikh [this message]
2013-09-19 13:40 ` chrubis
2013-10-14 5:33 ` Mike Frysinger
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=523AF319.50702@oracle.com \
--to=stanislav.kholmanskikh@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
/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.