-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does build.yaml
test-sim
test only the rv64gc/lp64d
bare-metal/newlib toolchain?
#1351
Comments
build.yaml
test-sim
test only the rv64gc/lp64d bare-metal/newlib toolchain?build.yaml
test-sim
test only the rv64gc/lp64d
bare-metal/newlib toolchain?
The
The
So, we have the following builds that are tested with QEMU:
And for Spike we have:
I think this is sufficient. |
Thanks @cmuellner - couldn't/shouldn't the
|
Yes, that would be a valid simplification. |
OK - thanks. I'll do a PR for this small change so. |
…x and remove unnecessary 'exclude' section
Rather than open a separate issue... Is there any reason why these jobs are run on Ubuntu 20.04 and not 22.04 (both are LTS releases)?
|
Sounds like a good PR! ;) |
Ok - I'll do that so. :-) Thanks. |
… unnecessary 'exclude' section
Both issues mentioned above addressed by this PR: |
See here:
riscv-gnu-toolchain/.github/workflows/build.yaml
Line 87 in 6b13243
And an example run here:
Why does the
test-sim
test only therv64gc/lp64d
bare-metal/newlib toolchain?Is this considered a sufficient test of the toolchain?
Why is Linux specified here:
riscv-gnu-toolchain/.github/workflows/build.yaml
Line 92 in 6b13243
but then excluded here:
riscv-gnu-toolchain/.github/workflows/build.yaml
Line 95 in 6b13243
Is this perhaps some legacy hangover - e.g. from when multiple simulators were used for testing or the Linux toolchain was tested?
Should this seeming redundancy be removed - e.g.:
The text was updated successfully, but these errors were encountered: