- 08 Apr, 2015 6 commits
-
-
- 07 Apr, 2015 2 commits
-
-
MARCHE Claude authored
-
MARCHE Claude authored
-
- 05 Apr, 2015 2 commits
-
-
Andrei Paskevich authored
-
MARCHE Claude authored
-
- 03 Apr, 2015 2 commits
-
-
MARCHE Claude authored
-
MARCHE Claude authored
-
- 02 Apr, 2015 6 commits
-
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
- 01 Apr, 2015 1 commit
-
-
MARCHE Claude authored
-
- 31 Mar, 2015 1 commit
-
-
Martin Clochard authored
-
- 28 Mar, 2015 2 commits
-
-
MARCHE Claude authored
-
MARCHE Claude authored
-
- 27 Mar, 2015 1 commit
-
-
Guillaume Melquiond authored
A child process (e.g. CVC4) might catch SIGXCPU. If it gets stuck then, it won't consume any additional cpu time, so the system won't forcibly kill it. So why3-cpulimit has to kill it. Note that, if the system is overloaded, why3-cpulimit might kill the child process before it has even reached its cpu time limit. Hopefully, the 60' additional time will suffice in practice.
-
- 26 Mar, 2015 1 commit
-
-
MARCHE Claude authored
-
- 25 Mar, 2015 7 commits
-
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
- 24 Mar, 2015 3 commits
-
-
-
Mário Pereira authored
-
MARCHE Claude authored
-
- 23 Mar, 2015 3 commits
-
-
Mário Pereira authored
-
MARCHE Claude authored
+ fixed wrong step limit in one session
-
Andrei Paskevich authored
-
- 22 Mar, 2015 3 commits
-
-
-
Mario Pereira authored
-
MARCHE Claude authored
-