Automated sync from github.com/tensorflow/tensorflow #640
TFLM-botpr_test.yml
on: pull_request_target
gatekeeper
3s
Matrix: call-core / call-ci-bazel / bazel_tests
Matrix: call-core / call-ci-makefile / x86_makefile_tests
Matrix: call-cortex-m / cortex_m_bluepill
call-check-tflite-files
/
Check PR Modifies TfLite Files
6s
call-core
/
...
/
Code Style
1m 21s
call-core
/
...
/
C++ Build Warnings
1m 53s
call-core
/
...
/
Project Generation
1m 48s
call-windows
/
Windows Bazel
10m 2s
call-windows
/
Windows Makefile
2m 43s
call-cortex-m
/
Cortex-M QEMU Unit Tests
1m 28s
call-cortex-m
/
Cortex-M Generic (GCC)
0s
call-cortex-m
/
Cortex-M Corstone 300 (GCC)
0s
call-cortex-m
/
Cortex-M Generic (Arm Clang)
0s
call-cortex-m
/
Cortex-M Corstone 300 (Arm Clang)
0s
call-xtensa
/
Vision P6 Build
3m 8s
call-xtensa
/
Hifi5 Unit Tests
2m 1s
call-xtensa
/
Hifi5 Unit Tests with Compression
2m 40s
call-xtensa
/
Hifi3z Unit Tests
2m 32s
call-xtensa
/
Hifi3z Unit Tests with Compression
3m 0s
call-xtensa
/
Fusion F1 Unit Tests
0s
call-xtensa
/
Vision P6 Unit Tests
0s
call-xtensa
/
Hifimini Unit Tests
0s
call-hexagon
/
Hexagon Build Test
1m 24s
call-riscv
/
RISC-V Tests
tests-passed
6s
Annotations
50 errors and 9 warnings
|
call-check-tflite-files / Check PR Modifies TfLite Files
Process completed with exit code 1.
|
|
call-cortex-m / Cortex-M Bluepill Release
Process completed with exit code 2.
|
|
call-cortex-m / Cortex-M Bluepill Renode
Process completed with exit code 2.
|
|
call-core / call-ci-makefile / Makefile x86 with Compression
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-makefile / Makefile x86 with Compression
Process completed with exit code 1.
|
|
call-core / call-ci-makefile / Makefile x86 with Compression
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 2."
|
|
call-cortex-m / Cortex-M Bluepill No Release
Process completed with exit code 2.
|
|
call-hexagon / Hexagon Build Test
Process completed with exit code 2.
|
|
call-core / call-ci-makefile / Makefile x86 Default
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-makefile / Makefile x86 Default
Process completed with exit code 1.
|
|
call-core / call-ci-makefile / Makefile x86 Default
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 2."
|
|
call-core / call-ci-misc / Project Generation
Process completed with exit code 2.
|
|
call-core / call-ci-makefile / Makefile x86 Release
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-makefile / Makefile x86 Release
Process completed with exit code 1.
|
|
call-core / call-ci-makefile / Makefile x86 Release
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 2."
|
|
call-core / call-ci-makefile / Makefile x86 No TFLite Static Memory
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-makefile / Makefile x86 No TFLite Static Memory
Process completed with exit code 1.
|
|
call-core / call-ci-makefile / Makefile x86 No TFLite Static Memory
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 2."
|
|
call-core / call-ci-makefile / Makefile x86 Out Of Tree
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-makefile / Makefile x86 Out Of Tree
Process completed with exit code 1.
|
|
call-core / call-ci-makefile / Makefile x86 Out Of Tree
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 2."
|
|
call-xtensa / Hifi5 Unit Tests
Process completed with exit code 2.
|
|
call-core / call-ci-misc / C++ Build Warnings
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-misc / C++ Build Warnings
Process completed with exit code 1.
|
|
call-core / call-ci-misc / C++ Build Warnings
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
|
|
call-xtensa / Hifi3z Unit Tests
Process completed with exit code 2.
|
|
call-xtensa / Hifi5 Unit Tests with Compression
Process completed with exit code 2.
|
|
call-windows / Windows Makefile
Process completed with exit code 2.
|
|
call-xtensa / Hifi3z Unit Tests with Compression
Process completed with exit code 2.
|
|
call-xtensa / Vision P6 Build
Process completed with exit code 2.
|
|
call-core / call-ci-bazel / Bazel with Compression [asan]
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-bazel / Bazel with Compression [asan]
Process completed with exit code 1.
|
|
call-core / call-ci-bazel / Bazel with Compression [asan]
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
|
|
call-core / call-ci-bazel / Bazel msan
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-bazel / Bazel msan
Process completed with exit code 1.
|
|
call-core / call-ci-bazel / Bazel msan
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
|
|
call-core / call-ci-bazel / Bazel asan
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-bazel / Bazel asan
Process completed with exit code 1.
|
|
call-core / call-ci-bazel / Bazel asan
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
|
|
call-core / call-ci-bazel / Bazel with Compression
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-bazel / Bazel with Compression
Process completed with exit code 1.
|
|
call-core / call-ci-bazel / Bazel with Compression
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
|
|
call-core / call-ci-bazel / Bazel
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-bazel / Bazel
Process completed with exit code 1.
|
|
call-core / call-ci-bazel / Bazel
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
|
|
call-core / call-ci-bazel / Bazel with Compression [msan]
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
call-core / call-ci-bazel / Bazel with Compression [msan]
Process completed with exit code 1.
|
|
call-core / call-ci-bazel / Bazel with Compression [msan]
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
|
|
call-windows / Windows Bazel
Process completed with exit code 1.
|
|
tests-passed
Process completed with exit code 1.
|
|
call-core / call-ci-misc / Project Generation
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-core / call-ci-misc / C++ Build Warnings
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-core / call-ci-bazel / Bazel with Compression [asan]
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-core / call-ci-bazel / Bazel msan
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-core / call-ci-bazel / Bazel asan
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-core / call-ci-bazel / Bazel with Compression
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-core / call-ci-bazel / Bazel
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-core / call-ci-bazel / Bazel with Compression [msan]
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-windows / Windows Bazel
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: bazel-contrib/setup-bazel@0.18.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|