Skip to content

fix: apply --max-odirs to RuntimeBackend as well#173

Open
AlexJones0 wants to merge 1 commit intolowRISC:masterfrom
AlexJones0:fix_max_odirs
Open

fix: apply --max-odirs to RuntimeBackend as well#173
AlexJones0 wants to merge 1 commit intolowRISC:masterfrom
AlexJones0:fix_max_odirs

Conversation

@AlexJones0
Copy link
Copy Markdown
Contributor

Fix a bug (only applies to the new experimental async scheduler, not yet in use) introduced in #134.

This --max-odirs argument was being applied in the command-line interface to the launchers, but the relevant logic was not ported to the RuntimeBackend base class when it was introduced.

This was being applied in the command-line interface to the launchers,
but the relevant logic was not ported to the `RuntimeBackend` base class
when it was introduced.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants