droidian rootfs-builder #1147
release.yml
on: schedule
Annotations
53 warnings
Generate matrix
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - armhf (api29)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - armhf (api29)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - armhf (api32)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - armhf (api32)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - armhf (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - armhf (api30)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - armhf (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - armhf (api28)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - armhf (api33)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - armhf (api33)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
sony_bahamut (phosh/phone edition) - arm64 (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
sony_bahamut (phosh/phone edition) - arm64 (api30)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
volla_yggdrasil (phosh/phone edition) - arm64 (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
volla_yggdrasil (phosh/phone edition) - arm64 (api28)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - arm64 (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - arm64 (api28)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - arm64 (api33)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - arm64 (api33)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
fxtec_pro1x (phosh/phone edition) - arm64 (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
fxtec_pro1x (phosh/phone edition) - arm64 (api30)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
volla_mimameid (phosh/phone edition) - arm64 (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
volla_mimameid (phosh/phone edition) - arm64 (api30)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - arm64 (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - arm64 (api30)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - arm64 (api29)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - arm64 (api29)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
rootfs (phosh/phone edition) - arm64 (api32)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
rootfs (phosh/phone edition) - arm64 (api32)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
fxtec_pro1 (phosh/phone edition) - arm64 (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
fxtec_pro1 (phosh/phone edition) - arm64 (api28)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
google_sargo (phosh/phone edition) - arm64 (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
google_sargo (phosh/phone edition) - arm64 (api28)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
xiaomi_miatoll (phosh/phone edition) - arm64 (api29)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
xiaomi_miatoll (phosh/phone edition) - arm64 (api29)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
Create GitHub release
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - armhf (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - armhf (api33)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - arm64 (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - armhf (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - arm64 (api29)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - arm64 (api33)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish volla_yggdrasil (phosh/phone edition) - arm64 (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish volla_mimameid (phosh/phone edition) - arm64 (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish fxtec_pro1 (phosh/phone edition) - arm64 (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish sony_bahamut (phosh/phone edition) - arm64 (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - arm64 (api32)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - armhf (api29)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - armhf (api32)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish rootfs (phosh/phone edition) - arm64 (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish google_sargo (phosh/phone edition) - arm64 (api28)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish xiaomi_miatoll (phosh/phone edition) - arm64 (api29)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Publish fxtec_pro1x (phosh/phone edition) - arm64 (api30)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
droidian-out-fxtec_pro1-arm64-phosh-phone-28
Expired
|
1.41 GB |
|
droidian-out-fxtec_pro1x-arm64-phosh-phone-30
Expired
|
1.44 GB |
|
droidian-out-google_sargo-arm64-phosh-phone-28
Expired
|
1.35 GB |
|
droidian-out-rootfs-arm64-phosh-phone-28
Expired
|
1.3 GB |
|
droidian-out-rootfs-arm64-phosh-phone-29
Expired
|
1.31 GB |
|
droidian-out-rootfs-arm64-phosh-phone-30
Expired
|
1.29 GB |
|
droidian-out-rootfs-arm64-phosh-phone-32
Expired
|
1.3 GB |
|
droidian-out-rootfs-arm64-phosh-phone-33
Expired
|
1.29 GB |
|
droidian-out-rootfs-armhf-phosh-phone-28
Expired
|
1.22 GB |
|
droidian-out-rootfs-armhf-phosh-phone-29
Expired
|
1.23 GB |
|
droidian-out-rootfs-armhf-phosh-phone-30
Expired
|
1.22 GB |
|
droidian-out-rootfs-armhf-phosh-phone-32
Expired
|
1.23 GB |
|
droidian-out-rootfs-armhf-phosh-phone-33
Expired
|
1.21 GB |
|
droidian-out-sony_bahamut-arm64-phosh-phone-30
Expired
|
1.44 GB |
|
droidian-out-volla_mimameid-arm64-phosh-phone-30
Expired
|
1.37 GB |
|
droidian-out-volla_yggdrasil-arm64-phosh-phone-28
Expired
|
1.4 GB |
|
droidian-out-xiaomi_miatoll-arm64-phosh-phone-29
Expired
|
1.46 GB |
|