this results in my storybook job running on the runner self-hosted but the triggered pages build and deployment is running on the github hosted ubuntu-lastest or whatever.
this is an issue because the runner is timing out due to upload size/artifact count (presumably)
Relevant links
Public repository: not public
YAML config: see above
YAML workflow: see above
Relevant log output
the workflow has the annotation
The hosted runner 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.
can't even read the logs for the upload artifacts step because there are so many it crashes my browser :)
Checklist
Describe your question
is it possible to use a self hosted runner for the
pages build and deployment
workflow that this triggers?here's my job snippet
i skipped all the fun stuff.
this results in my
storybook
job running on the runnerself-hosted
but the triggeredpages build and deployment
is running on the github hostedubuntu-lastest
or whatever.this is an issue because the runner is timing out due to upload size/artifact count (presumably)
Relevant links
Relevant log output
the workflow has the annotation
The hosted runner 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.
can't even read the logs for the
upload artifacts
step because there are so many it crashes my browser :)Additional context.
No response