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

Reduce 349 #355

Closed
wants to merge 2 commits into from
Closed

Reduce 349 #355

wants to merge 2 commits into from

Conversation

andreaTP
Copy link
Collaborator

@andreaTP andreaTP commented May 28, 2024

Opening this PR for 2 reasons:

  • it shows a valid way to reduce a fuzz reproducer
  • it goes full circle, using wasm-interp from the wabt tools to compare with the bare result of Chicory

Supersede #349

@andreaTP
Copy link
Collaborator Author

We still need to fix the Chicory CLI output to match wasmtime.

@@ -321,6 +321,17 @@ public void issue294_BRTABLE() {
assertEquals(4, main.apply()[0].asInt());
}

@Test
public void fuzzCrashReproY4ye0lx() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused. What is this supposed to test? Since all the tests pass, it's not crashing.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test demonstrates that the interpreter is emitting the correct result, and the problem is in "mimicking" the wasmtime output.
I will follow up on this eventually, I'm considering moving to wasm-interp as an "Oracle" as it has a better handling of Wasm types.

@andreaTP
Copy link
Collaborator Author

We need first to re-enable the fuzz tests based on wasm-interp

@andreaTP andreaTP closed this Oct 22, 2024
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 this pull request may close these issues.

3 participants