[
https://issues.apache.org/jira/browse/BEAM-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174686#comment-17174686
]
Beam JIRA Bot commented on BEAM-7749:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Establish a strategy to prevent or mitigate quota-related flakes in Beam
> integration tests.
> -------------------------------------------------------------------------------------------
>
> Key: BEAM-7749
> URL: https://issues.apache.org/jira/browse/BEAM-7749
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Valentyn Tymofieiev
> Priority: P2
> Labels: stale-P2
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
