-
-
Notifications
You must be signed in to change notification settings - Fork 4
CI: Adding CI to test old CPU for SIMD compatibility via SDE Emulation #59
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
|
Will add the patch, in a different PR to keep the diff under control |
ngoldbaum
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, if you feel like it you can probably avoid repeating yourself a bit, see comments.
.github/workflows/test_old_cpu.yml
Outdated
| workflow_dispatch: | ||
|
|
||
| jobs: | ||
| test_sandy_bridge: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only if you care to mess with it: I bet you can make a build matrix like:
strategy:
matrix:
build-arch: [
['sandy_bridge', 'Sandy Bridge (x86_64-v2)'],
['haswell', 'Haswell (x86_64-v3)'],
]
And then reduce the definition to use only one job definition and rely on the build matrix to generate the two almost-identical jobs.
.github/workflows/test_old_cpu.yml
Outdated
| run: | | ||
| pip install . --no-build-isolation -v | ||
| - name: Test import on Haswell (x86-64-v3) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo, it's x86_64 with an underscore.
|
Ah this matrix will cancel the v3 job if v2 got failed, let me search for a workaround if exists |
|
Cool, now it works |
|
Cool, merging this, this require some modifications for new commits in #62 so will do those changes there itself |
This workflow emulates the SandyBridge (x86-64-v2) and Haswell (x86-64-v3)
And similar to #56 we can reproduce the failure because of unrecognized instruction in SandyBridge