Skip to content
CI

use jiwer instead of evaluate in benchmarks (#1159) #739

Sign in to view logs

use jiwer instead of evaluate in benchmarks (#1159)

use jiwer instead of evaluate in benchmarks (#1159) #739

Triggered via push November 20, 2024 20:51
@MahmoudAshraf97MahmoudAshraf97
pushed 9c8ef76
master
Status Success
Total duration 1m 56s
Artifacts –

ci.yml

on: push
check-code-format
26s
check-code-format
run-tests
1m 30s
run-tests
build-and-push-package
9s
build-and-push-package
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
check-code-format
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
run-tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-push-package
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/