Skip to content

Don't require empty objects when referencing custom components #5365

Don't require empty objects when referencing custom components

Don't require empty objects when referencing custom components #5365

You are viewing an older attempt in the history of this workflow run. View latest attempt.
Triggered via pull request November 18, 2024 19:27
Status Failure
Total duration 9m 38s
Artifacts

build.yml

on: pull_request
Matrix: Build
markdown-link-check  /  markdown-link-check
36s
markdown-link-check / markdown-link-check
misspell-check  /  misspell-check
8s
misspell-check / misspell-check
publish-snapshots${{ ((((github.ref_name != 'main') || (github.repository != 'open-telemetry/opentelemetry-java')) && ' (skipped)') || '') }}
0s
publish-snapshots${{ ((((github.ref_name != 'main') || (github.repository != 'open-telemetry/opentelemetry-java')) && ' (skipped)') || '') }}
required-status-check
0s
required-status-check
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Build (ubuntu-latest, 21)
Process completed with exit code 1.
required-status-check
Process completed with exit code 1.
build-graal
Please remove "components: 'native-image'" from your workflow file. It is automatically included since GraalVM for JDK 17: https://github.com/oracle/graal/pull/5995

Artifacts

Produced during runtime
Name Size
coverage-report
3.52 MB