Bug#502311: testsuite failures in glibc
On Mon, Feb 23, 2009 at 11:26:01AM +0100, Sven Joachim wrote:
> On 2009-02-23 08:01 +0100, Aurelien Jarno wrote:
>
> > On Sun, Feb 22, 2009 at 11:48:55AM +0100, Sven Joachim wrote:
> >> All but one of these errors are fixed or ignored in 2.9-2, but the last
> >> problem still occurs -- apparently only if a 64-bit kernel is running
> >> and detectable. From my debuild log:
> >>
> >> ,----
> >> | #
> >> | # Testsuite failures, someone should be working towards
> >> | # fixing these! They are listed here for the purpose of
> >> | # regression testing during builds.
> >> | # Format: <Failed test>, Error <Make error code> [(ignored)]
> >> | #
> >> | annexc.out, Error 1 (ignored)
> >> | check-localplt.out, Error 1
> >> | tst-cancelx4.out, Error 1
> >> | tst-cancelx5.out, Error 1
> >> | tst-cpuclock2.out, Error 1
> >> | tst-tables.out, Error 1
> >> | ***************
> >> | Encountered regressions that don't match expected failures:
> >> | tst-tables.out, Error 1
> >> `----
> >>
> >> This does not happen if the build is run under linux32. The
> >> corresponding error message looks like this:
> >>
> >> ,----
> >> | /bin/bash tst-tables.sh /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/ /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/ > /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/tst-tables.out
> >> | Testing ASCIItst-table.sh:38: command not found: tst-table-charmap.sh
> >> | *** FAILED ***
> >> | make[3]: *** [/usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/tst-tables.out] Error 1
> >> `----
> >
> > This is not something I am able to reproduce here, either with bash or
> > dash. This problems also looks very strange, it's a shell script not
> > able to find another one, and I have problem to understand how the linux
> > personality can affect that.
>
> You're right. The problem is not related to that at all. Rather, I ran
> the original build with "debuild" but than retried with
> "linux32 debian/rules build" to save the recompilation time. The
> difference in the environment (most notably, debuild unsetting SHELL) is
> the problem.
What is your shell pointing to when not running under debuild? /bin/zsh?
> > The best to debug that is probably to pass -x to the shell, which should
> > gives some more debugging input.
>
> Did that and got this result:
>
> ,----
> | /bin/bash tst-tables.sh /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/ /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/ > /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/tst-tables.out
> | + common_objpfx=/usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/
> | + objpfx=/usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/
> | + status=0
> | + cat
> | + read charset charmap
> | + test '#' = GB18030
> | + case ${charset} in
> | + continue
> | + read charset charmap
> | + test '#' = GB18030
> | + case ${charset} in
> | + continue
> | + read charset charmap
> | + test '#' = GB18030
> | + case ${charset} in
> | + continue
> | + read charset charmap
> | + test '#' = GB18030
> | + case ${charset} in
> | + continue
> | + read charset charmap
> | + test ASCII = GB18030
> | + case ${charset} in
> | + echo -n 'Testing ASCII'
> | Testing ASCII+ /bin/zsh tst-table.sh /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/ /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/ ASCII ANSI_X3.4-1968
Seems zsh used.
> | tst-table.sh:38: command not found: tst-table-charmap.sh
> | + echo 'failed: ./tst-table.sh /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/ /usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/ ASCII ANSI_X3.4-1968'
> | + echo ' *** FAILED ***'
> | *** FAILED ***
> | + exit 1
> | + exit 1
> | make[3]: *** [/usr/local/src/deb-src/glibc/glibc-2.9/build-tree/i386-libc/iconvdata/tst-tables.out] Error 1
> `----
>
> Line 38 of tst-table.sh reads
>
> ${SHELL} tst-table-charmap.sh ${charmap:-$charset} \
> < ../localedata/charmaps/${charmap:-$charset} \
> > ${objpfx}tst-${charset}.charmap.table
>
> and with SHELL unset, it would try to run tst-table-charmap.sh directly,
> which isn't found in $PATH. This can be easily remedied, e.g. with
You tell before that the problem occurs when not running under debuild,
that is when SHELL *is* set. That's conflicting.
I am currently unable to reproduce the problem here.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: