Ichthyostega 8056bebf9c Scheduler: allow to manipulate nominal full capacity ... While building increasingly complex integration tests for the Scheduler, it turns out helpful to be able to manipulate the "full concurreency" as used by Scheduler, WorkForce and LoadController. In the current test, I am facing a problem that new entries from the threadsafe entrance queue are not propagated to the priority queue soon enough; partly this is due to functionality still to be added (scaling up when new tasks are passed in) -- but this will further complicate the test setup.		2023-11-07 16:12:56 +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	Library: switch Microbenchmark setup to C++17 threads	2023-09-24 18:07:28 +02:00
scheduler-activity-test.cpp	Scheduler: rectify λ-post API	2023-10-23 01:48:46 +02:00
scheduler-commutator-test.cpp	Scheduler: draft high-level API for building a Job schedule	2023-11-06 06:00:00 +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: allow to manipulate nominal full capacity	2023-11-07 16:12:56 +01:00
scheduler-service-test.cpp	Scheduler: allow to manipulate nominal full capacity	2023-11-07 16:12:56 +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
work-force-test.cpp	Scheduler: rectify λ-post API	2023-10-23 01:48:46 +02:00