[Pkg-gauche-devel] some make check failures in the buildd logs

NIIBE Yutaka gniibe at fsij.org
Mon Feb 7 08:07:37 UTC 2011


2011-02-07 16:46, Jens Thiele wrote:
> will you look into this?
> (i noted that you disabled that test, for now.)

I looked into this (It is reproducible on my machine).

For my case, it failed because the client variable 'sock' is bound to
IPv6 address, but make-server-socket returns the socket which only
bounds to IPv4 address.

> This is not good enough (it only exits the subshell)
[...]
> don't use subshell:
> $ dash -c 'for i in $(seq 1 10); do { echo $i ; exit 1 ; } ; done'
> 1

Thanks.  I will use this no subshell version.

Now, my idea is that:
	
	We only apply this exit status checking for Makefile of top
	directory, so that we can stop test failure of gc (which is
	fatal if we have some failure).

	We don't apply exit status checking for Makefiles under
	subdirectories, but check the content of TESTRECORD
	(test.record) after all of tests finished.

Besides, I see floating point failure on big endian machine and abort
because of no /dev/tty for all buildd machines.
-- 



More information about the Pkg-gauche-devel mailing list