[GitHub] [beam] damccorm opened a new issue, #19685: Establish a strategy to prevent or mitigate quota-related flakes in Beam integration tests.

[GitBox <gi...@apache.org>]

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

   Every now and then our postcommit tests fail due to lack of quota in apache-beam-testing, see [1].
   
   Filing this as an umbrella issue to establish a strategy for preventing quota-related failures in Apache Beam tests. 
   
   Potential ideas:
   - improve resilience of test infrastructure to retry tests that fail due to lack of quota, or delay the test execution when quota limits fall below a threshold
   - monitor & procure the quota usage in apache-beam-testing
   - tune the parameters affecting the number of concurrent test jobs according to available quota, and document best practices.
   - stop previous jenkins job that were triggered on a PR when a new job is started. 
   
   [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20component%20%3D%20test-failures%20AND%20text%20~%20quota
   
   Imported from Jira [BEAM-7749](https://issues.apache.org/jira/browse/BEAM-7749). Original Jira may contain additional context.
   Reported by: tvalentyn.


-- 
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: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org