-
Notifications
You must be signed in to change notification settings - Fork 116
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
Update shader tests after LLVM update #2835
Conversation
Update shader tests after a set of upstream changes in inst-combine. Last patch in the set is 5271d330770573d2df772aa0fa50d958f44400aa llvm/llvm-project#66787 Disable affected tests in this patch. TODO: re-enable tests once everything has propagated.
Not specific to this PR, but maybe we should improve on how we keep track of disabled tests, e.g. by requiring to open an issue? This is a git blame on currently disabled tests, some of these commits are quite old and mention to "soon enable tests again" once the update has propagated:
Produced by:
|
Test summary for commit 530aa41CTS tests (Failed: 0/138443)
Ubuntu navi3x, SrdcvkUbuntu navi2x, Srdcvk |
FWIW, we’d like to simply |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM too
@jasilvanus Yes, I think that's a good idea. Would you mind doing that? |
I'd rather have one GitHub issue per commit above assigned to the authors, so we can make progress in re-enabling tests and closing issues. I can create the initial ones if others feel positive about this. |
I wonder if it makes sense for one person to try fixing all of them in one go - and then filing issues for any that still fail? |
I tried re-enabling the tests. Some now work. See #2838 |
I have opened issues for the remaining tests, see the referenced issues. |
Update shader tests after a set of upstream changes in inst-combine. Last patch in the set is 5271d330770573d2df772aa0fa50d958f44400aa llvm/llvm-project#66787
Disable affected tests in this patch.
TODO: re-enable tests once everything has propagated.