Skip to content
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

Closed
y-guyon opened this issue Feb 22, 2024 · 4 comments · Fixed by #2034
Assignees

Comments

@y-guyon
Copy link
Collaborator

y-guyon commented Feb 22, 2024

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:

unknown file: error: SEH exception with code 0xc000001d thrown in the test body.

The following tests FAILED:
	 11 - avifchangesettingtest (Failed)
	 17 - avifgainmaptest (Failed)
	 24 - aviflosslesstest (Failed)
	 39 - avify4mtest (Failed)
	 46 - test_cmd_progressive (Failed)
@y-guyon
Copy link
Collaborator Author

y-guyon commented Feb 22, 2024

A possibly unrelated log entry is

Error: Svt[error]: deinit called without sending EOS!

@jzern
Copy link
Collaborator

jzern commented Feb 22, 2024

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.

@wantehchang wantehchang self-assigned this Feb 22, 2024
@wantehchang
Copy link
Collaborator

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.)

@wantehchang
Copy link
Collaborator

I found my experimental pull request: #1933. It was for AppVeyor.

wantehchang added a commit to wantehchang/libavif that referenced this issue Feb 22, 2024
The libaom change is temporary, until the Visual Studio 2022 bug is
fixed.

The libyuv change is permanent.

Fix AOMediaCodec#2033.
wantehchang added a commit to wantehchang/libavif that referenced this issue Feb 22, 2024
The libaom change is temporary, until the Visual Studio 2022 bug is
fixed.

The libyuv change is permanent.

Fix AOMediaCodec#2033.
wantehchang added a commit that referenced this issue Feb 22, 2024
The libaom change is temporary, until the Visual Studio 2022 bug is
fixed.

The libyuv change is permanent.

Fix #2033.
vrabaud pushed a commit to vrabaud/libavif that referenced this issue Feb 23, 2024
The libaom change is temporary, until the Visual Studio 2022 bug is
fixed.

The libyuv change is permanent.

Fix AOMediaCodec#2033.
vrabaud pushed a commit to vrabaud/libavif that referenced this issue Feb 23, 2024
The libaom change is temporary, until the Visual Studio 2022 bug is
fixed.

The libyuv change is permanent.

Fix AOMediaCodec#2033.
vrabaud added a commit to vrabaud/libavif that referenced this issue Jun 5, 2024
The CI started failing like in
AOMediaCodec#2033
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants