Skip to content

Handling generic data classes when determining identifier stability #3736

Handling generic data classes when determining identifier stability

Handling generic data classes when determining identifier stability #3736

Triggered via pull request May 15, 2024 17:23
Status Cancelled
Total duration 15m 42s
Artifacts 1

PR.yml

on: pull_request
Determine workflows to run
5s
Determine workflows to run
Matrix: test_linux
Matrix: test_mac
Waiting for pending jobs
Final PR results
0s
Final PR results
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
test_linux (jvmTest) / run-tests
Process completed with exit code 1.
test_linux (androidNativeX86TestKlibrary androidNativeX64TestKlibrary androidNativeArm32TestKlibr... / run-tests
FailFast: cancelling since parallel instance has failed
test_linux (:kotest-framework:kotest-framework-multiplatform-plugin-gradle:test) / run-tests
FailFast: cancelling since parallel instance has failed
Final PR results
Process completed with exit code 1.
test_linux (jvmTest) / run-tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "error-report". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
error-report
672 KB