Skip to content
CI

feat(tracing): using tracing instead of log #194

Sign in to view logs

feat(tracing): using tracing instead of log

feat(tracing): using tracing instead of log #194

Triggered via pull request April 3, 2024 13:26
@gabrikgabrik
synchronize #58
feat/tracing
Status Failure
Total duration 3m 38s
Artifacts –

ci.yml

on: pull_request
Matrix: build
CI status checks
0s
CI status checks
Matrix: Publish JVM snapshot package / builds
Waiting for pending jobs
Publish Android snapshot package  /  Publish Android Package to Github Packages
Publish Android snapshot package / Publish Android Package to Github Packages
Publish JVM snapshot package  /  Publish JVM package
Publish JVM snapshot package / Publish JVM package
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Build on ubuntu-latest
Process completed with exit code 101.
Build on macOS-latest
Process completed with exit code 101.
CI status checks
Process completed with exit code 1.
Build on ubuntu-latest
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-java@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build on macOS-latest
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-java@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.