Re: Testsuite problem when HOME is not defined

2016-12-02 Thread Chet Ramey 
On 12/1/16 2:38 PM, Vladimir Marek wrote:
> 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 it's worth
> adding something similar officially?

Yes, I will add something along these lines.

Chet


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

Testsuite problem when HOME is not defined

2016-12-01 Thread Vladimir Marek 
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 it's worth
adding something similar officially?

Thank you
-- 
Vlad
If $HOME is not set (running from cron perhaps), the tests will output:
26d25
< ./comsub-posix.tests: line 103: cd: HOME not set
28d26
< ./comsub-posix.tests: line 106: cd: HOME not set
--- tests/comsub-posix.tests2016-11-29 03:41:57.414081235 +
+++ tests/comsub-posix.tests2016-11-29 03:36:30.425718528 +
@@ -1,4 +1,5 @@
-
+HOME=${HOME:-/}
+export HOME
 # works right
 echo ab$(echo mnop)yz
 # works right