MartijnVisser opened a new pull request, #28313: URL: https://github.com/apache/flink/pull/28313
## What is the purpose of the change `MinioTestContainerTest` fails deterministically on `release-1.20` (and on every PR targeting it, e.g. #28306). The `flink-filesystems` CI stage runs on JDK 8, and the cached amd64 MinIO image has a `Created` timestamp with a colon timezone offset and sub-millisecond precision (e.g. `2022-09-25T13:46:35.209299016+08:00`) that the Jackson bundled in testcontainers cannot parse under JDK 8. `release-2.0` and later are unaffected because their filesystems stage runs on JDK 17, which parses the same value fine. The Azure docker-image cache key hashes `DockerImageVersions.java`, so the stale cached image keeps being restored on every run. Bumping the tag changes that key, invalidating the cache and forcing a fresh pull of a clean (UTC `Z`) image. `RELEASE.2022-02-12T00-51-25Z` is the next release, keeps the same single-drive `server /data` run mode, and its amd64 `Created` is `2022-02-13T19:39:51.252179004Z`. ## Brief change log - Bump `DockerImageVersions.MINIO` from `RELEASE.2022-02-07T08-17-33Z` to `RELEASE.2022-02-12T00-51-25Z`. ## Verifying this change This change is covered by the existing `flink-s3-fs-base` container tests (`MinioTestContainerTest` and others), which currently fail on `release-1.20`. ## Does this pull request potentially affect one of the following parts: No. ## Documentation No. Generated-by: Claude Code (Opus 4.8) -- 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]
