summaryrefslogtreecommitdiff
path: root/testsuite/timeout/timeout.hs
Commit message (Collapse)AuthorAgeFilesLines
* Remove the definition of die, which is now provided by System.ExitSimon Peyton Jones2014-04-281-4/+0
|
* Fix the timeout program following the changes to baseIan Lynagh2012-06-201-2/+0
|
* cleaning of testsuiteDavid Terei2011-11-151-1/+2
|
* Fix passing spaces to tests on Windows, and add a test for itIan Lynagh2011-10-181-2/+6
|
* Add some diagnostics to timeoutIan Lynagh2009-10-131-3/+9
|
* Do not use System.Process on Posix systemsSimon Marlow2008-12-221-27/+27
| | | | | | We were using System.Process.Internals, which isn't safe in general. Also, when the child process dies with a signal, we now raise the same signal ourselves.
* Change the timeout program to use exceptions properlyIan Lynagh2008-08-031-19/+30
| | | | We now don't eat any type of exception, e.g. the user pressing ^C
* Follow extensible exception changesIan Lynagh2008-06-231-6/+7
|
* Fix #1599: Improve timeout on WindowsIan Lynagh2008-01-201-43/+52
| | | | | We now run programs in a Job, which means that we can kill a process and all of its children when a timeout happens.
* Print something to stderr when a timeout happensIan Lynagh2007-03-041-109/+111
| | | | Also fixes whitespace.
* Allow testsuite to run under MSYS/MinGW using native Python (not Cygwin Python).brianlsmith2006-09-171-2/+5
| | | | | | | | | | | | | This patch is based on a similar one "Enable timeout in Windows and don't require cygwin python" by Esa Ilari Vuokko. It seems like timeout is always built on Windows so I rearranged the logic there to make the code clearer, Esa's patch required the user to uncomment the MinGW-specific logic in order for it to work; this patch does not have the MinGW-specific logic commented out. I tested this on the trunk in Ubuntu 6.06 on i686 (VMWare). I tested this on the trunk and ghc-6.6 branch on Windows i686.
* attempt to work around restrictions with fork() & pthreadsSimon Marlow2006-03-231-5/+12
| | | | | | | | | In the child process, call exec() directly instead of using System.Cmd.system, which involves another fork()/exec() and a non-blocking wait. The problem is that in a forked child of a threaded process, it isn't safe to do much except exec() according to POSIX. In fact calling pthread_create() in the child causes the pthread library to fail with an error on FreeBSD.
* [project @ 2005-11-23 11:47:16 by simonmar]simonmar2005-11-231-10/+11
| | | | Fix up to compile after recent changes to System.Process.Internals
* [project @ 2005-11-11 12:02:40 by simonmar]simonmar2005-11-111-5/+34
| | | | Make it work on Windows again.
* [project @ 2005-08-04 12:22:17 by simonmar]simonmar2005-08-041-25/+69
| | | | | | | | | | | | A better timeout. This one starts a new session for the child process, and attempts to kill the entire group when the time expires (previously we only killed the direct child, if the child itself had spawned more processes these would continue to run). The new scheme is only for Unix, presumably we have to do something different on Windows. Code partly from Ian Lynagh.
* [project @ 2005-02-04 10:59:55 by simonmar]simonmar2005-02-041-0/+25
Add a timeout to test runs, using a wrapper program (written in Haskell, using System.Process of course!).