[ 
https://issues.apache.org/jira/browse/BEAM-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Valentyn Tymofieiev updated BEAM-7714:
--------------------------------------
    Priority: Critical  (was: Blocker)

> Allow retries of PostCommit test suites per Python version
> ----------------------------------------------------------
>
>                 Key: BEAM-7714
>                 URL: https://issues.apache.org/jira/browse/BEAM-7714
>             Project: Beam
>          Issue Type: Sub-task
>          Components: testing
>            Reporter: Valentyn Tymofieiev
>            Assignee: Valentyn Tymofieiev
>            Priority: Critical
>             Fix For: Not applicable
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Currently Python PostCommit test executes 4 tests running the set of tests 
> under Python 2.7, 3.5-3.7. When test execution fails due to a flake, 
> contributors have to rerun the whole suite. Having a possibility to re-run 
> test suite only for a particular version of Python would make it easier to 
> receive a green run. 
> Some considerations:
>   - increasing number of Jenkins job will increase the number of slots 
> required by postcommit, this will slow down the queue, unless we increase 
> number of slots. We can investigate utilization of Jenkins workers to see if 
> slot increase is advisable.
> - we could introduce phrase-only suites "Run Python 3.7 PostCommits", that 
> will be separate jenkins jobs (1 suite, 1 slot) in addition to current jobs. 
> phrase-only suites will not be triggered on the PR but will be triggered 
> manually when users want to re-run tests for particular version. It may cause 
> confusion on a PR though, since PR author will have to explain to reviewers 
> that Python 3 Postcommit suite failed, but only 3.6 portion failed, and I 
> re-ran Py3.6 portion only in this separate jenkins Job and it passed, so PR 
> is safe to merge.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to