[
https://issues.apache.org/jira/browse/FLINK-34360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814707#comment-17814707
]
Matthias Pohl commented on FLINK-34360:
---------------------------------------
Essentially, we had 84G with 60G used by GitHub in the old setup (before Feb 2,
2024) and 73G with ~60G used by GitHub in the new setup. There's a drop of free
disk space from 24G to 13-14G.
Interestingly, Azure Pipeline runners seem to have 73G as well (see [example
build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57317&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=43ba8ce7-ebbf-57cd-9163-444305d74117&l=100]).
But the Azure runners seem to have less used disk space which seems to be the
reason why we're not running into issues there.
> 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)
