This is the mail archive of the
mailing list for the glibc project.
Re: run one test
- From: DJ Delorie <dj at redhat dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Wed, 25 Sep 2019 17:18:17 -0400
- Subject: Re: run one test
"Carlos O'Donell" <firstname.lastname@example.org> writes:
> Does this avoid rebuilding *anything* else?
It uses the internal dependency tree to generate the *.out file, but
does not artificially limit what that tree might rebuild.
> One of the problems with the suggested fix on the wiki is that it can
> put your tree into a bad state because of missing dependencies you
> might rebuild only part of glibc and fail.
> For example if $t.out depends on libpthread.so, then what happens
> if you've touched a file under nptl/? Likewise for libdl.so?
It does not do the implied "make" that "make check" does, if that's what
you're asking. It literally just reruns the one test - rebuilding the
test itself if needed, but not rebuilding libc.so because there's no
dependency on it.
So you'd need to run "make && make onetest t=..." if you want to rebuild
> And I suggest 'make onecheck' to match 'make xcheck' and 'make check' :-)
Let the bikeshedding begin! :-)