-
Notifications
You must be signed in to change notification settings - Fork 188
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
ci-windows failure "unknown file: error: SEH exception with code 0xc000001d thrown in the test body" #2033
Comments
A possibly unrelated log entry is
|
I think that's a code for illegal instruction. Visual Studio 2022 has an issue starting at 17.8.0 which might cause AVX-512 instructions to be emitted in non-AVX-512 code. This was labeled fixed in 17.10 Preview 1. |
Thanks for filing this bug report. We can consider compiling libaom with clang-cl until this Visual Studio 2022 bug is fixed. I will write a pull request to try that. (I remember I wrote an experimental pull request to do this before.) |
I found my experimental pull request: #1933. It was for AppVeyor. |
The libaom change is temporary, until the Visual Studio 2022 bug is fixed. The libyuv change is permanent. Fix AOMediaCodec#2033.
The libaom change is temporary, until the Visual Studio 2022 bug is fixed. The libyuv change is permanent. Fix AOMediaCodec#2033.
The libaom change is temporary, until the Visual Studio 2022 bug is fixed. The libyuv change is permanent. Fix #2033.
The libaom change is temporary, until the Visual Studio 2022 bug is fixed. The libyuv change is permanent. Fix AOMediaCodec#2033.
The libaom change is temporary, until the Visual Studio 2022 bug is fixed. The libyuv change is permanent. Fix AOMediaCodec#2033.
The CI started failing like in AOMediaCodec#2033
Note that ci-windows has been failing since #2032.
It may be unrelated to that PR because the previous passing test used the cache while this PR used a full workflow, so it may be cache-related instead.
The errors seem consistent across across the forks of this repository:
The text was updated successfully, but these errors were encountered: