Skip to content
Rolling Downstream Build

Deactivate controllers with command interfaces to hardware on DEACTIVATE #734

Sign in to view logs

Deactivate controllers with command interfaces to hardware on DEACTIVATE

Deactivate controllers with command interfaces to hardware on DEACTIVATE #734

Triggered via pull request June 25, 2025 16:30
@MarqRazzMarqRazz
synchronize #2334
MarqRazz:deactivate_controllers
Status Cancelled
Total duration 30s
Artifacts –

rolling-semi-binary-downstream-build.yml

on: pull_request
Matrix: build-downstream
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
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/2334/merge exists
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/2334/merge exists
Rolling Downstream Build
Canceling since a higher priority waiting request for Rolling Downstream Build-refs/pull/2334/merge exists
Rolling Downstream Build
Canceling since a higher priority waiting request for Rolling Downstream Build-refs/pull/2334/merge exists
Rolling Downstream Build
Canceling since a higher priority waiting request for Rolling Downstream Build-refs/pull/2334/merge exists
build-downstream (kilted) / kilted testing
Failed to restore: getCacheEntry failed: Cache service responded with 503
build-downstream (rolling) / rolling testing
Failed to restore: getCacheEntry failed: Cache service responded with 503