We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Flaky EXCEPTION: No error scopes to pop. on:
EXCEPTION: No error scopes to pop.
cts:validation/createTexture:it_is_invalid_to_submit_a_destroyed_texture_before_and_after_encode={"destroyBeforeEncode":false,"destroyAfterEncode":false} cts:validation/createView:Using_defaults_validates_the_same_as_setting_values_for_only_1_array_layer={"format":"rgba8unorm"} cts:validation/createView:Using_defaults_validates_the_same_as_setting_values_for_only_1_array_layer={"arrayLayerCount":2} cts:validation/createView:Using_defaults_validates_the_same_as_setting_values_for_only_1_array_layer={"mipLevelCount":1} cts:validation/createView:creating_cube_map_texture_view={"dimension":"cube","arrayLayerCount":6} cts:validation/createView:creating_cube_map_texture_view={"dimension":"cube","arrayLayerCount":7} cts:validation/error_scope:errors_bubble_to_the_parent_scope_if_not_handled_by_the_current_scope= cts:validation/error_scope:if_an_error_scope_matches_an_error_it_does_not_bubble_to_the_parent_scope= cts:validation/fences:increasing_fence_value_by_more_than_1_succeeds~ cts:validation/queue_submit:submitting_with_a_mapped_buffer_is_disallowed=
Might be a Chrome bug, unclear.
The text was updated successfully, but these errors were encountered:
I saw this while running all tests at once on http://localhost:8080/?q=cts:validation/ .
Sorry, something went wrong.
Easy repro: press the run button several times quickly
Almost certainly due to Chrome returning the same Dawn device for every WebGPU device right now.
Pretty sure this is gone.
No branches or pull requests
Flaky
EXCEPTION: No error scopes to pop.
on:Might be a Chrome bug, unclear.
The text was updated successfully, but these errors were encountered: