-
Notifications
You must be signed in to change notification settings - Fork 3k
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
slice operator implementation for webgpu native #23264
base: main
Are you sure you want to change the base?
Conversation
"^test_center_crop_pad_crop_negative_axes_hwc*", // failed due to new types or shape infer with negative axis for CenterCropPad. | ||
"^test_center_crop_pad_crop_negative_axes_hwc_expanded*" // failed due to new types or shape infer with negative axis for CenterCropPad. |
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.
are these 2 lines related to Slice?
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.
Yes, CenterCropPad is a function op that uses Slice in its definition.
I was seeing the following error in the MacOS CI Pipeline which I believe is because in the failing test the input has 3 dimensions but the cropping shape has 2. There is precedent set by other providers (like under current_failing_tests_OPENVINO_CPU_FP32) to skip this test due to the shape inference discrepancy.
[ONNXRuntimeError] : 1 : FAIL : Non-zero status code returned while running Slice node. Name:'' Status Message: WebGPU validation failed. Error while parsing WGSL: :61:30 error: index 2 out of bounds [0..1]
let steps_2 = uniforms.steps[2];
Increases operator coverage for webgpu native ep