Jonathan Nieder <jrnieder@xxxxxxxxx> writes:
> Matthieu Moy wrote:
>> "Vallon, Justin" <Justin.Vallon@xxxxxxxxxx> writes:
>
>>> --- a/t/t3404-rebase-interactive.sh
>>> +++ b/t/t3404-rebase-interactive.sh
>>> @@ -71,8 +71,9 @@ test_expect_success 'setup' '
>>> # "exec" commands are ran with the user shell by default, but this may
>>> # be non-POSIX. For example, if SHELL=zsh then ">file" doesn't work
>>> # to create a file. Unseting SHELL avoids such non-portable behavior
>>> -# in tests.
>>> +# in tests. It must be exported for it to take effect where needed.
>>> SHELL=
>>> +export SHELL
>>
>> (my bad, I wrote this SHELL= without exporting it. Since bash
>> re-exports already exported variables when they are assigned, and my
>> /bin/sh points to bash, I didn't notice)
>
> Isn't that how export works in all Bourne-style shells? For example:
>
> $ env var=outside dash -c '
> var=inside;
> dash -c "echo \$var"
> '
> inside
> $
>
> Maybe in the failing case SHELL was not exported but just set to
> /bin/false in .bashrc or similar?
Thanks, you saved me some time responding ;-)
Matthieu's diagnosis is only half correct in that bash is why he didn't
notice the problem, but if in this sequence
var=foo
export var
var=bar
some-command
some-command does not see "bar" as the value of environment variable
"var", your shell is not POSIX (there is no such thing as "re-exporting").
Either a variable is marked with the export attribute, in which case the
processes spawned from the shell sees the value of the then-current shell
variable in their environments, or they don't for shell variables that are
not marked with the export attribute.
The real reason the problem went unnoticed was because bash automatially
marks SHELL with the export attribute.
Because POSIX shells are required to mark variables they inherit from the
environment with the export attribute, your tests will run with SHELL
exported to the environment if your usual shell is bash (i.e. SHELL is
already exported to processes it spawns), even if you use another POSIX
shell to run your git and tests. That makes the issue doubly harder to
notice.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html