Skip to content
Elm Test

Run analyzer on the elm repo in the CI #167

Sign in to view logs

Run analyzer on the elm repo in the CI

Run analyzer on the elm repo in the CI #167

Triggered via pull request November 16, 2023 12:27
@jiegilletjiegillet
synchronize #74
jie-analyze-all-exercises
Status Success
Total duration 1m 43s
Artifacts –

elm_tests.yml

on: pull_request
build
18s
build
check-website-copy-paths
9s
check-website-copy-paths
smoke-test
1m 32s
smoke-test
analyze-elm-repo-solutions
1m 3s
analyze-elm-repo-solutions
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
check-website-copy-paths
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@e2f20e631ae6d7dd3b768f56a5d2af784dd54791. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@e2f20e631ae6d7dd3b768f56a5d2af784dd54791. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
smoke-test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@e2f20e631ae6d7dd3b768f56a5d2af784dd54791. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/