Added port constrain to list scheduler, added example and updated tests
All threads resolved!
All threads resolved!
-
Added port constrain to list scheduler, so that user can specify an upper bound on memory accesses.
-
Changed so that if the user does not specify a constraint on Inputs/Outputs they will be assumed to be 1. (This in order to prepare for doing the same thing for resources)
-
Added example showcasing the memory constraining.
-
Placed current tests into a unit test folder.
-
Added two integration tests going from SFG generation to architecture.
-
Bumped the timeout from 20s to 30s for the pipeline.
(Also, now that we have split testing we could add another stage in the CI for it.)
Closes: #302 (closed) #282 (closed)
Edited by Simon Bjurek
Merge request reports
Activity
added Scheduling Testing labels
assigned to @simbj106
requested review from @oscgu95
- Resolved by Simon Bjurek
- Resolved by Simon Bjurek
- Resolved by Simon Bjurek
Please register or sign in to reply