This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH buildbot] keep build directory after failure
- From: Szabolcs Nagy <Szabolcs dot Nagy at arm dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Cc: nd <nd at arm dot com>, Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>
- Date: Fri, 9 Nov 2018 11:16:16 +0000
- Subject: Re: [PATCH buildbot] keep build directory after failure
- References: <firstname.lastname@example.org>
On 02/11/18 11:33, Szabolcs Nagy wrote:
> aarch64 buildbot failed with
> FAIL: malloc/tst-malloc-tcache-leak
> 4 times so far even though there were no related commits,
> the failure happens about 1 out of 15 builds and only if
> the build was done in an unclean directory, but i could
> not manually reproduce it yet.
this is most likely caused by a cgroup task limit.
is there a known safe task limit setting for make check -j1 ?
the current setting is
$ cat /sys/fs/cgroup/pids/user.slice/user-1002.slice/pids.max
it also caused other failures
env GCONV_PATH=.... /home/szabolcs/tx1-ubuntu-aarch64/glibc-aarch64-linux/build/build/nptl/tst-eintr1 >
../scripts/evaluate-test.sh nptl/tst-eintr1 $? false false >
/bin/sh: 2: Cannot fork
make: *** [/home/szabolcs/tx1-ubuntu-aarch64/glibc-aarch64-linux/build/build/nptl/tst-eintr1.out] Error 2
> the buildbot first builds glibc in the previous build
> directory, if that fails then that immediately gets
> deleted and glibc is rebuilt starting from an empty
> build directory, so it's impossible to tell what went
> wrong in case of such non-reproducible failures.
> i suggest keeping the last failed build directory for
> the build directory rename is not optimal since that
> breaks absolute paths pointing to it (e.g. paths in
> testrun.sh), but it allows looking at test outputs
> and failed binaries.