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

   ### What happened?
   
   Release workflow's spanner test stage has experienced timeout, previously 
taking 1.5h on Oct 2, 
https://github.com/GoogleCloudPlatform/DataflowTemplates/actions/runs/37024273539
   
   It times out after 6h and blocking release since Oct 4
   
   
https://github.com/GoogleCloudPlatform/DataflowTemplates/actions/runs/37434003929
   
   
https://github.com/GoogleCloudPlatform/DataflowTemplates/actions/runs/37644942975
   
   Checking Spanner PR workflow, the number of integration test doesn't change 
much (198 to 207):
   
   
https://github.com/GoogleCloudPlatform/DataflowTemplates/actions/runs/37207672406
   
   
https://github.com/GoogleCloudPlatform/DataflowTemplates/actions/runs/37776697659
   
   (though this is still a very large number consider the number of templates 
it tests. each template should have only a few integration test. Parameter 
space should be covered by unit and smoke tests)
   
   Probably caused by #4334
   
   
   
   ### Issue Failure
   
   Failure: Test is continually failing
   
   ### Issue Priority
   
   Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be 
sure the product is healthy)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [ ] 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: Prism 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