This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] test-in-container: Install locales into the test container
- From: Carlos O'Donell <carlos at redhat dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: fweimer at redhat dot com, libc-alpha at sourceware dot org
- Date: Fri, 12 Jul 2019 00:02:26 -0400
- Subject: Re: [PATCH] test-in-container: Install locales into the test container
- References: <xn5zoarcfh.fsf@greed.delorie.com>
On 7/9/19 7:54 PM, DJ Delorie wrote:
"Carlos O'Donell" <carlos@redhat.com> writes:
Where do you draw the line?
Originally I wanted the "make install" to trigger just before the first
test that actually needed it, but I found it very difficult to do that.
Eventually more and more tests will run inside the container, and that
optimization would be useless anyway.
Perhaps we could at least add $(PARALLELMFLAGS) to the "make install" ?
If it's not already propogated by some other means? Or otherwise
optimize the install process, to limit the overhead during testing?
My point is that no matter how good you optimize, eventually there will
be enough tests that the time will creep up again.
I want Florian to be productive, and I want a build system that supports
a straight forward edit/build/test workflow.
My question is: How long is too long to wait for the results of testing
when you are doing a edit/build/test/debug cycle?
Should 'make check' be running enough tests to fill X seconds?
--
Cheers,
Carlos.