On 16.08.22 12:20, Neil C Smith wrote:
On Tue, 16 Aug 2022 at 09:25, Neil C Smith <[email protected]> wrote:
On Thu, 11 Aug 2022 at 14:20, Michael Bien <[email protected]> wrote:
The branch tests run on the head of the delivery branch
(refs/head/delivery). The sync PR tests run on the pending result of
the merge to the base branch (refs/pull/<ID>/merge), eg. master.
The above assumption might need checking. Just restarting a
pull-request test on the sync PRs and noticed that it restarted in
both - ie. two sync PRs with different base branches share a single
set of tests on both GitHub and Travis. At the moment, it's the
result of the merge to master, so the important one. Not sure how
consistent the behaviour is - workflow history shows the other one
cancelled.
OK, this is probably due to
https://github.com/apache/netbeans/pull/3932 I guess we need to group
by head and base ref?
yeahhh... maybe. This is making my head smoke thinking about all
scenarios this workflow has to deal with.
current logic is really simple:
if there is a github.head_ref
cancel other run with the same head_ref if there is one
start this run and group it as head_ref
else
group by github.run_id which is an UID which means "always run"
you can probably just restart one workflow/job if the other finishes as
workaround, right? :)
-mbien
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
