Author: jimb
Date: Tue Oct 24 05:58:27 2006
New Revision: 674
Modified:
trunk/TODO
Log:
Note that stress testing is useful even when
single-threaded. Bump
its priority.
Modified: trunk/TODO
============================================================
==================
--- trunk/TODO (original)
+++ trunk/TODO Tue Oct 24 05:58:27 2006
 -86,6
+86,13
* Environments should not rely on incoherent sections for
their mutual
exclusion.
+* For tests that don't actually communicate between
threads, add
+ "torture test" that runs them in many threads
over and over. Then
+ let the regression tests run single-threaded (and
faster!) by
+ default. It'd even be useful to run tests over and over
in a single
+ thread: it would show leaks and maybe catch bugs
sensitive to when
+ GC occurs.
+
==== prd.txt item 6 ("implement Core Scheme")
finished
-116,14
+123,10
and c-api-strings.
* New test stress-pair.c: build random trees, trade pieces
between
-threads, then replay whole process and check that the
results are as
-we expected. To make inter-thread trades reproducible,
have each
-thread record the sequence of other threads it traded with,
and then
-in the replay wait only for that thread.
-
-* For tests that don't actually communicate between
threads, add
- "torture test" that runs them in many threads
over and over. Then let
- the regression tests run single-threaded (and faster!) by
default.
+ threads, then replay whole process and check that the
results are as
+ we expected. To make inter-thread trades reproducible,
have each
+ thread record the sequence of other threads it traded
with, and then
+ in the replay wait only for that thread.
* Need tests for strings with embedded null characters.
_______________________________________________
Minor mailing list
Minorred-bean.com
http:/
/www.red-bean.com/mailman/listinfo/minor
|