[
https://issues.apache.org/jira/browse/FLINK-34360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814693#comment-17814693
]
Matthias Pohl commented on FLINK-34360:
---------------------------------------
There was a drop in available disk space from 84G (see [workflow run from Feb
2|https://github.com/apache/flink/actions/runs/7750406652/job/21136823036#step:14:11726])
to 73G (a [workflow run from the day
afterwards|https://github.com/apache/flink/actions/runs/7763815214/job/21176570116#step:14:11074]).
Looks like we're now close to the disk space that is required by certain tests
because we still have succeeding e2e1 runs with the disk space being at 73G
(see [most-recent
example|https://github.com/apache/flink/actions/runs/7793652557/job/21253945170#step:14:11788]).
> GHA e2e test failure due to no space left on device error
> ---------------------------------------------------------
>
> Key: FLINK-34360
> URL: https://issues.apache.org/jira/browse/FLINK-34360
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 1.19.0, 1.18.1
> Reporter: Matthias Pohl
> Priority: Major
> Labels: github-actions, test-stability
>
> https://github.com/apache/flink/actions/runs/7763815214
> {code}
> AdaptiveScheduler / E2E (group 2)
> Process completed with exit code 1.
> AdaptiveScheduler / E2E (group 2)
> You are running out of disk space. The runner will stop working when the
> machine runs out of disk space. Free space left: 35 MB
> {code}
> We're only seeing it in GHA which makes me think that it's rather a
> GHA-related issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
