github/ci Make Spike64-2 tests run regardless of Spike32 tests result #888
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
MarekVCodasip
force-pushed
the
ci-run-spike64-if-spike32-failed
branch
from
36ffadb
to
a12900a
Compare
This patch separates the Spike tests into their own jobs and makes them run regardless of the results of the previous test. Previously, if Spike32 tests failed, Spike64-2 tests did not even run. This can be an issue if new tests are added in the riscv-tests repository which are not yet passing on riscv-openocd. Change-Id: I0bdaee5fbbba5582babab40f176cfab49660c246 Signed-off-by: Marek Vrbka <[email protected]>
MarekVCodasip
force-pushed
the
ci-run-spike64-if-spike32-failed
branch
from
a12900a
to
deb0d91
Compare
MarekVCodasip
changed the title
JanMatCodasip
approved these changes
Jul 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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 patch separates the Spike tests into their own jobs and makes them run regardless of the results of the previous test. Previously, if Spike32 tests failed, Spike64-2 tests did not even run. This can be an issue if new tests are added in the riscv-tests repository which are not yet passing on riscv-openocd.
Change-Id: I0bdaee5fbbba5582babab40f176cfab49660c246