delegate: skip external_test if ubsan is enabled ubsan is currently failing due to `-fsanitize=function` in this test. As referenced in the comment, this seems to be due to a different configuration when building that binary & this one. Skipping the test on ubsan builds until that's fixed seems like the best balance for now. BUG=b:433670501 TEST=`FEATURES=test emerge-amd64-generic tensorflow` passes Disallow-Recycled-Builds: test-failures Change-Id: I2f7cbf2365845f65cc597844c7fcde6a09319a85 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/tflite/+/6897788 Commit-Queue: George Burgess <gbiv@chromium.org> Reviewed-by: Tommy Chiang <ototot@google.com> Tested-by: George Burgess <gbiv@chromium.org>
This repository hosts the core ChromeOS TFLite components, enabling on-device machine learning (ODML) workloads accelerated by NPU.
The corresponding ebuild can be found at: tensorflow-9999.ebuild
Patches are stored in the patch/ directory and explicitly listed in WORKSPACE.bazel. A helper script, ./script/patcher.py, is included to facilitate patch management within a TFLite workspace.
The typical workflow:
Eject (Download) TensorFlow Source Code
Download the TensorFlow source code into a local git repository with patches applied as individual commits:
./script/patcher.py eject
This creates a new local git repository at tensorflow/.
Modify the TensorFlow Repository
Make changes to the tensorflow/ repository as needed, following standard git workflows. Optionally, include a PATCH_NAME= tag in commit messages to specify the filename of the corresponding patch.
Seal the Repository
Regenerate the patch files and update the WORKSPACE.bazel file:
./script/patcher.py seal
This updates the patches in the patch/ directory and reflects the changes in WORKSPACE.bazel.
It's preferred to submit changes to upstream TensorFlow first and cherry-pick them as patches. This helps minimize divergence and makes TensorFlow updates easier.