[ci] split SoftwareFrameworkTests from simple testbench simulation #820
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
umarcor
force-pushed
the
umarcor/ci-processor-split
branch
from
361d53a to
fc81b10
Compare
|
This is now rebased, after merging #817. |
stnolting
approved these changes
Feb 21, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is based on #817
, so I'll keep it as a draft until that one is merged.Instead of building the processor check software together with other "toolchain testing software compilation" tasks, it is done at the same time the simulation is to be executed, in a separated job.
Moreover, since building the software and running the simulation was done using the same container image but in different steps (thus, spawning two containers), I changed it to call make target
sim-check(from #817) directly.By the way, I removed 'Container' from job names/ids, since currently all the steps are executed on containers. I believe that's just a leftover from some years ago, when the simple testbench was executed on GitHub's Ubuntu environment.