-
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
String Tensor SplitToSequence fix #19942
Conversation
/azp run Linux CPU CI Pipeline,Linux CPU Minimal Build E2E CI Pipeline,Linux GPU CI Pipeline,Linux GPU TensorRT CI Pipeline,Linux OpenVINO CI Pipeline,Linux QNN CI Pipeline,MacOS CI Pipeline,ONNX Runtime Web CI Pipeline,Windows ARM64 QNN CI Pipeline |
/azp run Windows CPU CI Pipeline,Windows GPU CI Pipeline,Windows GPU TensorRT CI Pipeline,Windows x64 QNN CI Pipeline,orttraining-linux-ci-pipeline,orttraining-linux-gpu-ci-pipeline,orttraining-ortmodule-distributed,onnxruntime-binary-size-checks-ci-pipeline |
Azure Pipelines successfully started running 8 pipeline(s). |
Azure Pipelines successfully started running 9 pipeline(s). |
The Windows GPU TensorRT failure says that it couldn't find a CUDA device in tests other than the one I added, and they don't appear at first glance to use SplitToSequence either. Maybe it hit some dodgy hardware? |
/azp run ONNX Runtime Web CI Pipeline,orttraining-amd-gpu-ci-pipeline,Big Models,Android CI Pipeline,iOS CI Pipeline,ONNX Runtime React Native CI Pipeline |
Azure Pipelines successfully started running 6 pipeline(s). |
Description
The SplitToSequence refactor added a special case for element_size when it's a string, but this stops the computation of the
A
offset on line 510 from advancing as the offset is zero. So it copies the same string into each sequence element. This PR removes that check and adds a test for the string split behaviour.I'm not sure why the special case on line 456 was added in the original PR (#18594), but all the tests pass in the new PR so presumably it isn't necessary.
Motivation and Context
SplitToSequence didn't work on string tensors, fixes #19726.
cc @pranavsharma