Ichthyostega 23a3a274ce Scheduler-test: investigate further breakage ... ...which turns out to be due to the DUMP-Statements, which seem to create quite some contention on their own. Test cases with very tight schedule will slip away then; without print statement everything is GREEN now		2023-12-12 01:55:52 +01:00
..
activity-detector-test.cpp	Scheduler: access invocation time for test	2023-10-25 23:40:47 +02:00
activity-detector.hpp	Scheduler-test: a helper for one-time operations	2023-12-08 03:16:57 +01:00
block-flow-test.cpp	Scheduler: connect BlockFlow capacity announcement	2023-11-10 23:52:20 +01:00
scheduler-activity-test.cpp	Scheduler / Activity-Lang: simplify handling of blocked Gate	2023-12-07 22:12:41 +01:00
scheduler-commutator-test.cpp	Scheduler: integrate sanity check on timings	2023-11-07 18:37:20 +01:00
scheduler-invocation-test.cpp	Scheduler: reconciled into clearer design	2023-11-04 04:49:13 +01:00
scheduler-load-control-test.cpp	Scheduler: connect BlockFlow capacity announcement	2023-11-10 23:52:20 +01:00
scheduler-service-test.cpp	Scheduler-test: investigate further breakage	2023-12-12 01:55:52 +01:00
scheduler-stress-test.cpp	Scheduler: plan for integration	2023-10-20 00:59:50 +02:00
scheduler-usage-test.cpp	Scheduler: plan for integration	2023-10-20 00:59:50 +02:00
special-job-fun-test.cpp	Scheduler-test: a helper for one-time operations	2023-12-08 03:16:57 +01:00
test-chain-load-test.cpp	Scheduler-test: ''can demonstrate running a synthetic load'' (closes #1346)	2023-12-11 23:53:25 +01:00
test-chain-load.hpp	Scheduler-test: --- instrumentation ---	2023-12-11 23:55:55 +01:00
work-force-test.cpp	Chain-Load: demonstrate use of the expansion rule	2023-11-29 02:58:55 +01:00