featzhang commented on PR #28096: URL: https://github.com/apache/flink/pull/28096#issuecomment-4366896970
Pushed an empty commit to trigger a fresh Azure CI run. **Root cause of build #74753 failure: infrastructure-level flaky, unrelated to this PR.** This PR only touches 4 files under `flink-runtime-web/web-dashboard/` (TypeScript / HTML / LESS). The build failed exclusively in the `Test - connect` stage, where `MinioTestContainerTest` (in `flink-s3-fs-base`) could not launch the `minio/minio:RELEASE.2022-02-07T08-17-33Z` Docker container: ``` MinioTestContainerTest.testBucketCreation » ContainerLaunch Container startup failed for image minio/minio:RELEASE.2022-02-07T08-17-33Z ... InvalidFormatException: Can not deserialize value of type java.util.Date from String "2022-09-25T13:46:35.209299016+08:00": not a valid representation (through reference chain: com.github.dockerjava.api.model.Network["Created"]) ``` The root cause is the Docker daemon on the Azure agent returning 9-digit nanosecond-precision timestamps that the shaded Jackson inside `testcontainers` cannot parse — a well-known CI infrastructure flaky on release-1.20. There is **zero overlap** between the failing module (`flink-s3-fs-base`) and the PR's web-UI diff. For reference, the identical diff on `release-2.1` (PR #28092) is already green. Preferring an empty commit over `@flinkbot run azure` because the latter just re-runs the same build on the same agent/commit hash, which tends to repeat the same infrastructure failure; a new commit hash forces flinkbot to schedule a brand-new Azure build on a fresh agent. The empty commit will be squashed on merge. -- 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]
