summaryrefslogtreecommitdiff
path: root/testsuite/timeout
Commit message (Collapse)AuthorAgeFilesLines
...
* Build the timeout program with CabalIan Lynagh2008-07-232-32/+51
|
* FIX boottestsuite build failureSimon Marlow2008-07-111-0/+3
|
* FIX BUILDSimon Marlow2008-07-071-0/+2
|
* Avoid using deprecated flags in the testsuite testsIan Lynagh2008-06-161-1/+1
|
* Add WinCBindings.hsc, not WinCBindings.hs!Ian Lynagh2008-01-202-193/+144
|
* Fix #1599: Improve timeout on WindowsIan Lynagh2008-01-203-44/+248
| | | | | We now run programs in a Job, which means that we can kill a process and all of its children when a timeout happens.
* small tidyups to thie MakefileSimon Marlow2007-11-161-5/+8
|
* Stop the timeout calibration ever returning 0Ian Lynagh2007-08-211-1/+4
|
* Fix calibrate python script for non-UNIX machinesIan Lynagh2007-07-071-1/+8
|
* Calibrate == calibrate on Windows...Ian Lynagh2007-04-063-4/+4
|
* Use $(PYTHON) to run calibrate, rather than relying on it finding python itselfIan Lynagh2007-04-051-2/+1
|
* Calibrate the testsuite timeout if a value of -1 is givenIan Lynagh2007-04-053-0/+33
|
* Print something to stderr when a timeout happensIan Lynagh2007-03-042-109/+112
| | | | 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.
* Use a python timeout for the testsuite when we don't have a threaded RTSIan Lynagh2006-09-072-0/+36
|
* 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-042-25/+73
| | | | | | | | | | | | 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-042-0/+37
Add a timeout to test runs, using a wrapper program (written in Haskell, using System.Process of course!).
View Lorry Controller Status