Draft
Conversation
Collaborator
|
Do we want this as a difftest? Should we create runtime tests using similar / the same stuff but not requiring a different impl to diff against? |
Member
Author
|
I was considering that... but when testing libs, it's probably still best to difftest it against calling the entry point from the CPU, to see if the GPU code may have mispiled somehow. |
Open
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
blake3 is failing with a bunch of ICEs, see #312. This is a repro of the failure within out difftest framework, so that a fix can be developed.
black_box error:
memset error, only locally observed: