chamikaramj opened a new issue, #32896:
URL: https://github.com/apache/beam/issues/32896

   ### What happened?
   
   First failure: 
   
   https://github.com/apache/beam/actions/runs/11445520520
   
   https://github.com/apache/beam/runs/31848196342
   
   ```
         if self._runtime_exception:
   >       raise self._runtime_exception
   E       RuntimeError: Pipeline 
BeamApp-runner-1021175329-11c8c557_04f95baf-bc86-48dc-954b-16138b058df3 failed 
in state FAILED: java.io.IOException: Received exit code 125 for command 
'docker run -d --network=host --env=DOCKER_MAC_CONTAINER=null 
apache/beam_java11_sdk:2.61.0.dev --id=1-2 
--provision_endpoint=localhost:41031'. stderr: Unable to find image 
'apache/beam_java11_sdk:2.61.0.dev' locallydocker: Error response from daemon: 
manifest for apache/beam_java11_sdk:2.61.0.dev not found: manifest unknown: 
manifest unknown.See 'docker run --help'.
   
   apache_beam/runners/portability/portable_runner.py:568: RuntimeError
   ```
   
   
   
   ### Issue Failure
   
   Failure: Test is flaky
   
   ### Issue Priority
   
   Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be 
sure the product is healthy)
   
   ### Issue Components
   
   - [X] Component: Python SDK
   - [X] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Infrastructure
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
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]

Reply via email to