Ichthyostega 1f2a635973 Chain-Load: get the first non-trivial topology to work ... ..as can be expected, had do chase down some quite hairy problems, especially since consumption of the fixed amount of nodes is not directly linked to the ''beat'' of the main loop and thus boundary conditions and exhausted storage can happen basically anywhere. Used a simple expansion rule and got a nod graph, which looks coherent in DOT visualisation.		2023-11-17 01:11:12 +01:00
..
activity-detector-test.cpp	Scheduler: access invocation time for test	2023-10-25 23:40:47 +02:00
activity-detector.hpp	Scheduler: wrap-up and comment test cases thus far	2023-10-27 03:37:24 +02:00
block-flow-test.cpp	Scheduler: connect BlockFlow capacity announcement	2023-11-10 23:52:20 +01:00
scheduler-activity-test.cpp	Scheduler: rectify λ-post API	2023-10-23 01:48:46 +02: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: high-level schedule-Render-Job test complete	2023-11-09 04:04:53 +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
test-chain-load-test.cpp	Chain-Load: get the first non-trivial topology to work	2023-11-17 01:11:12 +01:00
test-chain-load.hpp	Chain-Load: get the first non-trivial topology to work	2023-11-17 01:11:12 +01:00
work-force-test.cpp	Scheduler: rectify λ-post API	2023-10-23 01:48:46 +02:00