Skip to content

[DOCS] deploying custom elements #520

[DOCS] deploying custom elements

[DOCS] deploying custom elements #520

Triggered via pull request October 13, 2023 21:14
Status Success
Total duration 7m 11s
Artifacts

tests.yml

on: pull_request
Test RSConnect
3m 6s
Test RSConnect
Test Docker
3m 7s
Test Docker
Test no exra ml frameworks
48s
Test no exra ml frameworks
Test pydantic v1
1m 9s
Test pydantic v1
Matrix: Tests
Matrix: typecheck
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Tests (ubuntu-latest, 3.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (ubuntu-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (macos-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (windows-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/