Re: How to skip test when building glibc

[Letu Ren <fantasquex@gmail.com>]

Hi,

> It depends of what you are doing on your build script. The ‘make’ rule does
> not run unit unit test, so if you intend to just build glibc it should be suffice.

I'm currently trying to build glibc for ArchLinux RISC-V. My build
script executes `make` then `make check`. "It is highly recommended to
have check() as it helps to make sure software has been built
correctly and works fine with its dependencies." according to
ArchLinux wiki Creating packages. So I think I need to `make check`.

> However, if you are trying to run the expected make and make check you
> try to not run the tests itself with the extra ‘run-built-tests=no’ rule with
> ‘make check’.

As I'm new to libc, I'm not sure what `run-built-tests=no` does
exactly. I cannot find a wiki page which mentions this make variable.
I found some mail archives about it. "If you look at some of the
Makefiles in glibc, it conditionally includes/excludes some tests from
being built based on the value of run-built-tests.". And according to
glibc/Makeconfig, "Whether to run test programs built for the
library's host system." I wonder what this variable does exactly and
whether `make check run-built-tests=no` can make sure glibc built by
myself is able to work correctly.

> Unfortunately, there is no way to avoid specific tests in a default 'make check’
> and this is intentional: a failure really should represent an issue that might be
> investigated.
>
> We are trying to either get rid of flaky tests or improve them in a way to make
> them report robust output, to avoid environment issues that might mislead
> the runner.
>
> What kind of issue are you seeing in you environment?

I encountered 16 test failures. 11 of them are due to timeouts.
FAIL: nss/tst-nss-files-hosts-getent
FAIL: nss/tst-nss-files-hosts-multi
FAIL: string/test-memcpy
FAIL: string/test-memcpy-large
FAIL: string/test-mempcpy
FAIL: stdio-common/tst-vfprintf-width-prec
FAIL: stdio-common/tst-vfprintf-width-prec-mem
FAIL: resolv/tst-resolv-res_init-multi
FAIL: malloc/tst-malloc-too-large-malloc-hugetlb2
FAIL: nptl/tst-mutex10
FAIL: locale/tst-localedef-path-norm

 And Five of them are mentioned in release notes of glibc v2.35. So I
think those failures are expected.
FAIL: math/test-float-j0
FAIL: math/test-float32-j0
FAIL: stdlib/tst-strfrom
FAIL: stdlib/tst-strfrom-locale
FAIL: stdlib/test-bz22786

As far as I know, ArchLinux officially skips some tests using  sed in
Makefile. Just simply remove some tests. In my case, I cannot simply
sed, because I cannot find test-float-j0, which is generated in
runtime. I planned to execute `TIMEOUTFACTOR=300 make check` to make
sure no timeout issue occurs. So the only problem is how to deal with
five expected to fail tests. Could you please give me some advice?