Age | Commit message (Collapse) | Author | Files | Lines |
|
On systems where we aren't getting enough cpu time.
Heuristic check, but probably good enough in practice.
Fixes #282
Signed-off-by: Steve Bennett <steveb@workware.net.au>
|
|
If running in a VM with very variable time
Signed-off-by: Steve Bennett <steveb@workware.net.au>
|
|
This test is essentially the same as timer-6.4 except with
tighter timing requirements. Remove it to prevent spurious failures.
Signed-off-by: Steve Bennett <steveb@workware.net.au>
|
|
Speed up the timer and exec unit tests with smaller sleeps
Signed-off-by: Steve Bennett <steveb@workware.net.au>
|
|
Much closer to tcltest now, including constraints.
Try to get all appropriate tests running under both Jim and Tcl.
Signed-off-by: Steve Bennett <steveb@workware.net.au>
|
|
Signed-off-by: Steve Bennett <steveb@workware.net.au>
|
|
Move Jim_EvalObjBackground() out of the core to eventloop
Time events are now kept and triggered in time order
Time handlers are removed before execution
Add 'update'
Add 'after info' and 'after idle'
Include time events in the return from Jim_ProcessEvents()
Add Tcl eventloop tests
Signed-off-by: Steve Bennett <steveb@workware.net.au>
|