potiuk edited a comment on pull request #31104:
URL: https://github.com/apache/spark/pull/31104#issuecomment-758487194
> I enabled this only for the jobs triggered by PRs but there seems a bug in
the plugin. If the PR triggers the job cancelation, it cancels all the
workflows in the master branch too.
Not all - but 'all but the latest one'. This is by design.
This is not a bug. The plugin works 'aggressively' in `cancelAllDuplicates`
mode - whenever 'cancelAllDuplicates' is run, it will cancel all 'duplicated'
runs (all runs that match the same tuple: ('branch', 'oirigin repo', 'event')
- regardles which branch it is.
So for every PR and every branch (including `master`) it will only leave the
'latest build` running. All other will be cancelled. This is by design. The
most recent build from master should not be cancelled.
The assumption is that if you merged several merges to master, you really
want to run tests on the latest version of this - all the previous merges are
not 'valid' any more - they are superseded by the latest build.
In case of Airflow it saves hours of needless builds.. Is this a problem for
Spark ?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
