-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Creating SMACK github actions test runner #9461
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
Conversation
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
CodSpeed Performance ReportMerging #9461 will not alter performanceComparing Summary
Footnotes
|
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
Removed steps for checking out code and building GNU harness in the workflow.
|
Going to try the approach of just running the specific cli tools and back script directly instead of importing the entirety of the gnu library otherwise the complexity will grow tremendously |
|
GNU testsuite comparison: |
Updated QEMU configuration and added installation of coreutils.
Refactor SMACK-related GNU tests to use a bash heredoc for better readability and error handling.
|
GNU testsuite comparison: |
Three of the GNU tests are currently skipped because it requires begin run on a environment that has smack support. As we look to get 100% GNU test coverage, the only way that we currently can get SMACK on Github runners is either using QEMU or using a private test runner.
Ideally if this works out we can do the same thing to get RootFS support