On Fri, Dec 2, 2016 at 6:28 AM, Vladimir Marek
wrote:
> Hi,
>
> I'm not sure what is going on, but the bash test suite was getting
> stopped (as if SIGSTOP was received) in the middle. Trying to find
> minimal set of conditions it came to this:
>
> - my ~/.bashrc has
On 12/1/16 2:35 PM, Vladimir Marek wrote:
> Hi,
>
> during testing of latest bash on Solaris I found strange behavior. We
> run the tests with clear environment (env -). It seems to be caused by
> undefined SHELL variable. The test reported
>
> 150,151c150,151
> < ./redir11.sub: line 26: echo:
On 12/1/16 2:28 PM, Vladimir Marek wrote:
> Hi,
>
> I'm not sure what is going on, but the bash test suite was getting
> stopped (as if SIGSTOP was received) in the middle. Trying to find
> minimal set of conditions it came to this:
>
> - my ~/.bashrc has to contain 'cd /' (any dir works)
> -
On 12/1/16 3:21 PM, Vladimir Marek wrote:
> Hi,
>
> I am attaching patch against tests/run-all with the hope that the
> changes can be accepted upstream. The patch should be self explanatory.
> For completeness here are the errors I saw before I erased SHELLOPTS
> variable
I can see doing this.
Hi,
I am attaching patch against tests/run-all with the hope that the
changes can be accepted upstream. The patch should be self explanatory.
For completeness here are the errors I saw before I erased SHELLOPTS
variable
run-redir
warning: the text of a system error message may vary between
Hi,
On Solaris bash is compiled with --enable-xpg-echo-default=yes (and
--enable-usg-echo-default=yes if that makes difference). I have no idea
why, but since it was shipped like this for a long time, I am afraid of
changing that :)
Because of this setting the tests are failing. I am attaching a
In spirit similar problem to the previous one, when the tests are
executed with $HOME undefined, I was getting this error:
26d25
< ./comsub-posix.tests: line 103: cd: HOME not set
28d26
< ./comsub-posix.tests: line 106: cd: HOME not set
I am attaching the patch I am using for workaround, maybe
Hi,
during testing of latest bash on Solaris I found strange behavior. We
run the tests with clear environment (env -). It seems to be caused by
undefined SHELL variable. The test reported
150,151c150,151
< ./redir11.sub: line 26: echo: write error: Bad file number
< ./redir11.sub: line 27:
Hi,
I'm not sure what is going on, but the bash test suite was getting
stopped (as if SIGSTOP was received) in the middle. Trying to find
minimal set of conditions it came to this:
- my ~/.bashrc has to contain 'cd /' (any dir works)
- the tests have to first execute run-execscript, namely it