-
Notifications
You must be signed in to change notification settings - Fork 11
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
Change some of CI to do ARM testing #47
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
This reverts commit 4f08b6e. Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Ref: https://github.com/quantumlib/Stim/blob/main/doc/usage_command_line.md When `--seed #` is set, the exact same simulation results will be produced every time ASSUMING: - the exact same other flags are specified - the exact same version of Stim is being used - the exact same machine architecture is being used (for example, you're not switching from a machine that has AVX2 instructions to one that doesn't). Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
This reverts commit eb720e5.
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
The ARM segfault in the Solvers library (which in this case only appears on A100, not H100) appears to be the same as the known LLVM resolveAArch64Relocation issue. Here is the capture backtrace for posterity's sake. (The core file was captured on arm-a100 and then backtraced using a machine I could log into w/ H100.) A secondary issue we should figure out is why an LLVM assertion is appearing like a segfault in the Solver library because it would've made this much easier to assess if we had gotten the right error message out.
|
Test-only for now