Test maxStorage(Buffers/Textures)In(Fragment/Vertex)Stage #4133
Conversation
This file contains 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
greggman
force-pushed
the
maxStorageBuffersInFragmentStage
branch
from
ef118bb to
b7471fa
Compare
greggman
force-pushed
the
maxStorageBuffersInFragmentStage
branch
from
b7471fa to
7d66972
Compare
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.
On Chrome stable the tests are correctly skipped because the limits don't exist.
On Chrome canary the validate test in each fails because canary doesn't enforce that
maxXXXInYYYStagemust be less thanmaxXXXPerShaderStage. The auto_upgrade test already passes because of a recent CL.On a local build with this CL they all pass.