Hello, Result without SHELL=/bin/bash was unstable. I found (1) There was syslog message "WARNING: /tmp: File system full" (2) I'm testing on /tmp (3) Difference between with & without SHELL=/bin/bash starts from 154, such as < 154: listing sparse files bigger than 2^33 B skipped (sparse05.at:31) < 155: storing sparse file using seek method skipped (sparse06.at:32) --- > 154: listing sparse files bigger than 2^33 B testsuite: WARNING: > unable to parse test group: 154 > FAILED (sparse05.at:31) > 155: storing sparse file using seek method skipped ()
Tried again with % limit filesize 9000000 (more than 2^33 B, and enough /tmp space left) Then, have the same result even if without SHELL=/bin/bash, FAILED only in 92, 175 and 176. Can this be a hint ? --- Kiyoshi ----- Original Message ----- > From: Kiyoshi KANAZAWA <yoi_no_myou...@yahoo.co.jp> > To: "bug-tar@gnu.org" <bug-tar@gnu.org> > Cc: > Date: 2018/2/10, Sat 21:35 > Subject: [GNU tar 1.30] testsuite: 92 175 176 failed on Solaris11.3 x86 > > Hello, > > Trying to install GNU tar. > > % ./configure CC=gcc SHELL=/bin/bash > % make > passed. > % make check > has 3 failes. > > Tested on Solaris 11.3 x86/x64 with gcc 7.3.0. > testsuite logs are attached. > > > Without SHELL=/bin/bash in configure, have many fails in make check phase, > such as > > testsuite: 92 154 156 157 158 159 164 165 166 167 168 169 170 171 172 173 174 > 175 176 177 181 187 190 191 197 199 208 209 214 220 failed > > > FYI, /bin/bash is the default user shell on Solaris 11, > but /bin/sh is ksh. > % ls -l /bin/sh > lrwxrwxrwx 1 root root DATE /bin/sh -> amd64/ksh93 > > > Regards, > > --- Kiyoshi >
