[
https://issues.apache.org/jira/browse/SPARK-54739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-54739.
----------------------------------
Fix Version/s: 4.2.0
Resolution: Fixed
Issue resolved by pull request 53008
[https://github.com/apache/spark/pull/53008]
> Cancel PR build when a new commit is pushed
> -------------------------------------------
>
> Key: SPARK-54739
> URL: https://issues.apache.org/jira/browse/SPARK-54739
> Project: Spark
> Issue Type: Test
> Components: Project Infra
> Affects Versions: 4.2.0
> Reporter: Tian Gao
> Assignee: Tian Gao
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.2.0
>
>
> Currently when a user pushes a new commit to their PR, the old workflow will
> continue to run. Our workflow is slow and there is a concurrency limit for
> each user. The result is that without manual intervene, the user would have
> to wait for a long time before the latest commit can be checked. Also for
> most of the cases, the old commits are out of date and useless. We should
> cancel the old ones when a new commit is pushed.
> Notice that we've tried this before and got reverted. The reason is that the
> commits in apache/spark master are not validated simultaneously anymore. We
> should make sure that all the new commits in master are still checked as
> before, only the user PR is affected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
