Amar3tto commented on PR #37050: URL: https://github.com/apache/beam/pull/37050#issuecomment-3632842737
> Looking at failures: > > * [PreCommit Java ElasticSearch IO Direct](https://github.com/apache/beam/actions/runs/20040634643/job/57521862000?pr=37050) - failing because of [[Elasticsearch] Add support for v9.x #36670](https://github.com/apache/beam/pull/36670) which changed the workflow, but didn't make it onto the release branch. This should be harmless to ignore. > * [PreCommit Java GCP IO Direct](https://github.com/apache/beam/actions/runs/20040634689/job/57521648405?pr=37050) - not sure why this is failing and this requires further investigation. It looks like it was resolved on the master branch on Dec 1: https://github.com/apache/beam/actions/workflows/beam_PreCommit_Java_GCP_IO_Direct.yml?page=2&query=branch%3Amaster+event%3Aschedule > * The rest all are Dataflow issues, likely caused by the Dataflow containers not being published. > > AIs: > > * [ ] @shunping please follow go/beam-release#during-release to publish Dataflow containers > * [ ] @Amar3tto and @shunping please follow up and investigate why [PreCommit Java GCP IO Direct](https://github.com/apache/beam/actions/runs/20040634689/job/57521648405?pr=37050) is failing I think this is expected, please check my comment: https://github.com/apache/beam/pull/36919#issuecomment-3600240300 -- 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]
