The last round of refactorings yielded significant improvements - parallelisation now works as expected - processing progresses closer to the schedule - run time was reduced The processing load for this test is tuned in a way to overload the scheduler massively at the end -- the result must be correct non the less. There was one notable glitch with an assertion failure from the memory manager. Hopefully I can reproduce this by pressing and overloading the Scheduler more...
73 lines
973 B
Text
73 lines
973 B
Text
TESTING "Component Test Suite: Scheduler" ./test-suite --group=engine
|
|
|
|
|
|
|
|
TEST "Activity observation framework" ActivityDetector_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "BlockFlow memory management scheme" BlockFlow_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Scheduler Activity Language" SchedulerActivity_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Scheduler Layer-1" SchedulerInvocation_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Scheduler Layer-2" SchedulerCommutator_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Scheduler Load-Control" SchedulerLoadControl_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Scheduler Integration" SchedulerService_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Self-managed one-time Job" SpecialJobFun_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Synthetic Load for Test" TestChainLoad_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
PLANNED "Scheduler Performance" SchedulerStress_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
PLANNED "Scheduler Usage" SchedulerUsage_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Worker Thread Service" WorkForce_test <<END
|
|
return: 0
|
|
END
|