Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Executed bash thinks that bash-specific syntax is not supported #5

Closed
smspillaz opened this issue Mar 23, 2015 · 1 comment
Closed

Executed bash thinks that bash-specific syntax is not supported #5

smspillaz opened this issue Mar 23, 2015 · 1 comment

Comments

@smspillaz
Copy link
Contributor

Bash specific syntax is not supported in covered scripts, for instance, process substitution, e.g. echo "data" > >(my_function))

The reason for this is that bash's argv[0] is not "bash", but instead the environment variables prepended to it. This causes bash to drop back to sh-compatible mode.
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
c109b9b 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
@smspillaz smspillaz mentioned this issue Mar 23, 2015
Closed
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
1c3917a 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
0a198e4 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
287655d 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
787ac5b 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
e1c6abf 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
4160bbf 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
336ad2e 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
82f6d56 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
5cbf9de 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
@smspillaz smspillaz mentioned this issue Mar 23, 2015
Closed
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 23, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
c3bf88b 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
b3df56e 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
ed48982 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
be9eb13 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
4634fb5 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
f0f2329 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
ccb6553 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
6434a1f 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
a81dac2 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
47c1f74 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Use Process.spawn's internal mechanisms to set environment.
962c4ca 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes infertux#5
smspillaz added a commit to smspillaz/bashcov that referenced this issue Mar 24, 2015
@smspillaz
runner: Set the BASH_XTRACEFD and PS4 variables explicitly
bf5ec1f 
Set the BASH_XTRACEFD and PS4 variables explicitly as opposed
to setting them on the command line. If they are the first element
on the command line, argv[0] will not be "bash" and bash will
run in posix-compatible mode, which isn't always the desired
behaviour.

No tests can be provided, as the interaction between BASH_XTRACEFD
and bash-only syntax on BSD is flakey at best, which means that
tests will only pass a part of the time.

Fixes infertux#5
This was referenced Mar 24, 2015
Closed
Closed
infertux pushed a commit that referenced this issue Mar 24, 2015
@smspillaz @infertux
runner: Use Process.spawn's internal mechanisms to set environment.
cae7c99 
Don't set the environment as part of the command line as this
will modify argv[0]. This in turn confuses bash into think that
it is running in /bin/sh compatible mode and not /bin/bash mode.

Added a test to verify that we can get coverage on bashisms.

Fixes #5

Signed-off-by: Cédric Félizard <cedric@felizard.fr>
@infertux
Copy link
Owner

infertux commented May 5, 2015

Should be fixed in ca3c119.

@infertux infertux closed this as completed May 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@infertux @smspillaz