Skip to content

ci: Produce stacktraces for failing integration tests #202

ci: Produce stacktraces for failing integration tests

ci: Produce stacktraces for failing integration tests #202

Triggered via pull request July 24, 2023 23:41
Status Success
Total duration 1m 29s
Artifacts

pre-merge.yaml

on: pull_request
Gradle validation
6s
Gradle validation
Check *.kt *.kts with ktfmt
54s
Check *.kt *.kts with ktfmt
Run lint and detekt
1m 20s
Run lint and detekt
Run local tests for all projects
1m 12s
Run local tests for all projects
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Check *.kt *.kts with ktfmt
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run local tests for all projects
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run lint and detekt
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/