Skip to content

backport: nodes flooder (analyzer) from cs-ebot #313

backport: nodes flooder (analyzer) from cs-ebot

backport: nodes flooder (analyzer) from cs-ebot #313

Triggered via pull request April 24, 2023 21:16
@jeefojeefo
synchronize #439
analyze
Status Failure
Total duration 2m 50s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build.yml

on: pull_request
Matrix: bot-build
bot-build (windows-x86-msvc)
2m 36s
bot-build (windows-x86-msvc)
bot-release
0s
bot-release
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 4 warnings
bot-build (windows-x86)
Process completed with exit code 1.
bot-build (darwin-x86)
Process completed with exit code 1.
bot-build (linux-aarch64)
Process completed with exit code 1.
bot-build (linux-x86)
Process completed with exit code 1.
bot-build (windows-x86-gcc)
Process completed with exit code 1.
bot-build (linux-x86-gcc)
Process completed with exit code 1.
bot-build (windows-x86-msvc)
Process completed with exit code 1.
bot-build (windows-x86-msvc)
Failed to download action 'https://api.github.com/repos/actions/checkout/zipball/8e5e7e5ab8b370d6c329ec480221332ada57f0ab'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (codeload.github.com:443)
bot-build (windows-x86-msvc)
Back off 13.109 seconds before retry.
bot-build (windows-x86-msvc)
Failed to download action 'https://api.github.com/repos/actions/checkout/zipball/8e5e7e5ab8b370d6c329ec480221332ada57f0ab'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (codeload.github.com:443)
bot-build (windows-x86-msvc)
Back off 29.951 seconds before retry.