Skip to content

Fix the prepare_command_mode_switch behaviour when HW is INACTIVE #753

Fix the prepare_command_mode_switch behaviour when HW is INACTIVE

Fix the prepare_command_mode_switch behaviour when HW is INACTIVE #753

Triggered via pull request June 29, 2025 20:47
Status Cancelled
Total duration 2m 21s
Artifacts
Matrix: build-downstream
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 4 warnings
build-downstream (rolling) / rolling testing
Process completed with exit code 1.
build-downstream (rolling) / rolling testing
The operation was canceled.
build-downstream (rolling) / rolling testing
Canceling since a higher priority waiting request for Rolling Downstream Build-refs/pull/2347/merge exists
Rolling Downstream Build
Canceling since a higher priority waiting request for Rolling Downstream Build-refs/pull/2347/merge exists
Rolling Downstream Build
Canceling since a higher priority waiting request for Rolling Downstream Build-refs/pull/2347/merge exists
Rolling Downstream Build
Canceling since a higher priority waiting request for Rolling Downstream Build-refs/pull/2347/merge exists
build-downstream (kilted) / kilted testing
Process completed with exit code 1.
build-downstream (kilted) / kilted testing
The operation was canceled.
build-downstream (kilted) / kilted testing
Canceling since a higher priority waiting request for Rolling Downstream Build-refs/pull/2347/merge exists
build-downstream (rolling) / rolling testing
Failed to save: Tar failed with error: The process '/usr/bin/tar' failed with exit code 1
build-downstream (rolling) / rolling testing
Failed to restore: getCacheEntry failed: Cache service responded with 503
build-downstream (kilted) / kilted testing
Failed to save: Tar failed with error: The process '/usr/bin/tar' failed with exit code 1
build-downstream (kilted) / kilted testing
Failed to restore: getCacheEntry failed: Cache service responded with 503