MartijnVisser opened a new pull request, #29176:
URL: https://github.com/apache/flink/pull/29176
## What is the purpose of the change
FLINK-40224 moved `free_disk_space.sh` from `tools/azure-pipelines` to
`tools/ci` and updated `jobs-template.yml`, `e2e-template.yml` and the GitHub
action, but not `build-nightly-dist.yml`. Both `cron_snapshot_deployment` jobs
have therefore failed on every master nightly since:
```
./tools/azure-pipelines/free_disk_space.sh: No such file or directory
##[error]Bash exited with code '127'.
```
`cron_snapshot_deployment_binary` was last green in build 77434
(2026-07-25); build 77447 (2026-07-26) ran on the FLINK-40224 commit and it has
failed ever since, so no nightly binaries have been published for seven weeks.
It also means the disk-space fix from FLINK-40058 has not been running.
## Brief change log
- `build-nightly-dist.yml` calls `./tools/ci/free_disk_space.sh` in both
jobs
## Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
The only callers of the script are the two lines changed here; `git grep
free_disk_space` now shows every reference pointing at `tools/ci/`, the target
exists and is executable, and the file still parses as YAML.
Note that this only fixes `cron_snapshot_deployment_binary`.
`cron_snapshot_deployment_maven` has been failing since build 76959
(2026-07-10) for an unrelated reason tracked in FLINK-40145, and will start
failing there again once this path is corrected.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude Opus 5 (1M context)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
