Replace grep cpuinfo with nproc #693
T0biiifirmware.yml
on: pull_request
generate_target_matrix
3s
Matrix: build_firmware
create_release
0s
Annotations
48 errors
|
build_firmware (ath79-generic)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ath79-generic)
The operation was canceled.
|
|
build_firmware (lantiq-xrx200)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (lantiq-xrx200)
The operation was canceled.
|
|
build_firmware (mpc85xx-p1010)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (mpc85xx-p1010)
The operation was canceled.
|
|
build_firmware (ramips-mt7620)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ramips-mt7620)
The operation was canceled.
|
|
build_firmware (ath79-mikrotik)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ath79-mikrotik)
The operation was canceled.
|
|
build_firmware (lantiq-xway)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (lantiq-xway)
The operation was canceled.
|
|
build_firmware (ramips-mt7621)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ramips-mt7621)
The operation was canceled.
|
|
build_firmware (ramips-mt76x8)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ramips-mt76x8)
The operation was canceled.
|
|
build_firmware (ipq40xx-generic)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ipq40xx-generic)
The operation was canceled.
|
|
build_firmware (mvebu-cortexa9)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (mvebu-cortexa9)
The operation was canceled.
|
|
build_firmware (sunxi-cortexa7)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (sunxi-cortexa7)
The operation was canceled.
|
|
build_firmware (bcm27xx-bcm2708)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (bcm27xx-bcm2708)
The operation was canceled.
|
|
build_firmware (ath79-nand)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ath79-nand)
The operation was canceled.
|
|
build_firmware (x86-geode)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (x86-geode)
The operation was canceled.
|
|
build_firmware (rockchip-armv8)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (rockchip-armv8)
The operation was canceled.
|
|
build_firmware (x86-generic)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (x86-generic)
The operation was canceled.
|
|
build_firmware (ipq806x-generic)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ipq806x-generic)
The operation was canceled.
|
|
build_firmware (bcm27xx-bcm2710)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (bcm27xx-bcm2710)
The operation was canceled.
|
|
build_firmware (mediatek-mt7622)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (mediatek-mt7622)
The operation was canceled.
|
|
build_firmware (x86-legacy)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (x86-legacy)
Process completed with exit code 143.
|
|
build_firmware (ipq40xx-mikrotik)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (ipq40xx-mikrotik)
The operation was canceled.
|
|
build_firmware (bcm27xx-bcm2711)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
build_firmware (bcm27xx-bcm2711)
The operation was canceled.
|
|
build_firmware (mpc85xx-p1020)
The hosted runner: GitHub Actions 49 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build_firmware (bcm27xx-bcm2709)
The hosted runner: GitHub Actions 54 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build_firmware (realtek-rtl838x)
The hosted runner: GitHub Actions 15 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build_firmware (x86-64)
The hosted runner: GitHub Actions 5 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|