[NFC] Fix compiler warnings from TypeSwitch on AffineExpr (#16306) #29
ci.yml
on: push
setup
/
setup
7s
build_test_all_arm64
0s
build_test_all_windows
0s
build_test_all_macos_arm64
0s
build_test_all_macos_x86_64
0s
build_test_all_bazel
0s
build_test_runtime
0s
build_test_runtime_arm64
0s
build_test_runtime_windows
0s
python_release_packages
0s
asan
0s
tsan
0s
small_runtime
0s
gcc
0s
tracing
0s
debug
0s
byo_llvm
0s
build_e2e_test_artifacts
/
build_e2e_test_artifacts
Matrix: build_benchmark_tools / build_benchmark_tools
Waiting for pending jobs
Matrix: cross_compile_and_test
test_all
0s
test_gpu
0s
test_a100
0s
test_tf_integrations
0s
test_tf_integrations_gpu
0s
Matrix: test_benchmark_suites
Matrix: build_and_test_android / test
Waiting for pending jobs
Matrix: execution_benchmarks / run_benchmarks
Waiting for pending jobs
summary
12s
Annotations
19 errors and 2 warnings
build_test_all_macos_x86_64
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
|
build_test_all_arm64
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
build_test_all_macos_arm64
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
build_test_all_windows
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
asan
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
build_test_runtime
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
build_test_all_bazel
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
build_test_runtime_arm64
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
build_test_runtime_windows
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
byo_llvm
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
debug
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
gcc
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
python_release_packages
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
small_runtime
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
tsan
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
build_all / build_all
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
tracing
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
summary
Process completed with exit code 1.
|
summary
Unexpected failure: Error: no webhook is given (no webhook is given)
|
setup / setup
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
summary
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, sarisia/actions-status-discord@61114b793b460ee85fe38ad3fccc78c7ead38d55. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|