[
https://issues.apache.org/jira/browse/ATLAS-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044615#comment-18044615
]
ASF subversion and git services commented on ATLAS-5167:
--------------------------------------------------------
Commit 17deccc7f188cb2453d753c70a2dce1e89447d25 in atlas's branch
refs/heads/atlas-2.5 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=17deccc7f ]
ATLAS-5167: Fix failing Atlas ci build (#487)
(cherry picked from commit 59b5abae4d60bf1352800002d84492b4f9a5355b)
> Fix failing Atlas ci build
> --------------------------
>
> Key: ATLAS-5167
> URL: https://issues.apache.org/jira/browse/ATLAS-5167
> Project: Atlas
> Issue Type: Bug
> Components: atlas-ci-build
> Reporter: Pinal Shah
> Assignee: Pinal Shah
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *Issue:*
> Atlas github CI build are constantly failing with either 'no space left' or
> getting stuck at 'Bring up container' action
> *Error:*
> {code:java}
> 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. {code}
> or
> {code:java}
> System.IO.IOException: No space left on device :
> '/home/runner/actions-runner/cached/_diag/Worker_20251210-165559-utc.log' at
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
