Skip to content

We can have a tokenizer anywhere. #1219

We can have a tokenizer anywhere.

We can have a tokenizer anywhere. #1219

Triggered via pull request September 24, 2024 12:55
Status Cancelled
Total duration 58m 30s
Artifacts

ci_build.yaml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
build (cuda) / integration_tests
Canceling since a higher priority waiting request for 'CI build---omni_tokenizer' exists
build (intel-xpu) / build-and-push
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/build-push-action@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 (intel-cpu) / build-and-push
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/build-push-action@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 (rocm) / build-and-push
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/build-push-action@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 (cuda) / build-and-push
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/