Skip to content

General build upgrades and improvements #19

General build upgrades and improvements

General build upgrades and improvements #19

Triggered via pull request February 21, 2024 19:56
Status Failure
Total duration 13m 56s
Billable time 8m
Artifacts

on.pr.yml

on: pull_request
Pre-flight Checks
2m 39s
Pre-flight Checks
Matrix: Build / gradle
Checks  /  Dependency Review
15s
Checks / Dependency Review
Matrix: Checks / CodeQL
Matrix: Build / gradle
Fit to window
Zoom out
Zoom in

Annotations

8 errors, 3 warnings, and 1 notice
Checks / Formatting
Gradle build failed: see console output for details
Checks / Detekt
Path does not exist: build/reports/detekt/detekt.sarif
Build / Build (Ubuntu)
Process completed with exit code 1.
Checks / Dependency Review
Dependency review detected vulnerable packages.
Build / Native CLI (Windows)
invalid path 'pkl-core/src/test/files/LanguageSnippetTests/input-helper/globtest/\moduleC.pkl'
Build / Native CLI (Windows)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
Build / Native CLI (Ubuntu)
Gradle build failed: see console output for details
Build / Native CLI (macOS x64)
Gradle build failed: see console output for details
Build / Build (Ubuntu)
Submitted dependency-graph-reports/pr-gradle-ubuntu-strict-ubuntu-latest.json: The snapshot was accepted, but it is not for the default branch. It will not update dependency results for the repository.
Checks / CodeQL (java-kotlin)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
Checks / CodeQL (java-kotlin)
The "paths"/"paths-ignore" fields of the config only have effect for JavaScript, Python, and Ruby
Build / Native CLI (macOS aarch64)
Failed to generate-and-submit dependency graph. Will continue. Error: Dependency submission failed for dependency-graph-reports/pr-gradle-macos_aarch64-strict-macos-13-xlarge-pkl-climacexecutableaarch64.json. HttpError: Resource not accessible by integration Please ensure that the 'contents: write' permission is available for the workflow job. Note that this permission is never available for a 'pull_request' trigger from a repository fork.