This is the mail archive of the
mailing list for the glibc project.
Setting high test timeouts makes some tests take longer.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Mike Frysinger <vapier at gentoo dot org>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 26 Feb 2016 03:50:28 -0500
- Subject: Setting high test timeouts makes some tests take longer.
- Authentication-results: sourceware.org; auth=none
I noticed nptl/tst-exit2 taking longer and longer the more
I increased my timeouts.
If you look at the test it actually relies on the test to
timeout for it to complete! Yikes!
It uses pthread_exit to exit the main thread, and then it
proves the created thread is still running by timing out
These tests that have "EXPECTED_SIGNAL SIGALRM" (not all
of them, but several) need to be rewritten to use alarm()
to trigger the signal at some reasonable time instead of
the full duration of the test timeout.
So with your patch to increase timeouts, it makes
these tests take longer :-(
Do you think using alarm() is a good solution? Seems