Skip to content

fix: non absolute build paths are relative to the build manifest #6280

fix: non absolute build paths are relative to the build manifest

fix: non absolute build paths are relative to the build manifest #6280

Triggered via pull request November 25, 2024 23:38
@nhtyynhtyy
synchronize #1819
n/build
Status Cancelled
Total duration 2m 7s
Artifacts

pr.yml

on: pull_request
Matrix: Low Memory
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 2 warnings
CLI
Canceling since a higher priority waiting request for 'PR-1819' exists
Low Memory (32)
Canceling since a higher priority waiting request for 'PR-1819' exists
Low Memory (64)
Canceling since a higher priority waiting request for 'PR-1819' exists
Test (x86-64)
Canceling since a higher priority waiting request for 'PR-1819' exists
Performance
Canceling since a higher priority waiting request for 'PR-1819' exists
Formatting & Clippy
Canceling since a higher priority waiting request for 'PR-1819' exists
Check lock files
Canceling since a higher priority waiting request for 'PR-1819' exists
Low Memory (16)
Canceling since a higher priority waiting request for 'PR-1819' exists
Low Memory (16)
The operation was canceled.
Test (ARM)
Canceling since a higher priority waiting request for 'PR-1819' exists
Test (ARM)
The operation was canceled.
Examples
Canceling since a higher priority waiting request for 'PR-1819' exists
Examples
The operation was canceled.
Spell Check
The following actions uses node12 which is deprecated and will be forced to run on node16: getsentry/action-git-diff-suggestions@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Spell Check
The following actions use a deprecated Node.js version and will be forced to run on node20: getsentry/action-git-diff-suggestions@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/