[Dune-devel] change to ci on branches?

[Dedner, Andreas]

Hi.
Just wanted to raise this issue again (forgot to raise it at the dev-meeting).
This is probably also causing the pipelines in dune-istl to fail for this MR
https://gitlab.dune-project.org/core/dune-istl/-/merge_requests/538
Does anyone have an idea what might going on?

Best
Andreas

________________________________
From: Dedner, Andreas <A.S.Dedner at warwick.ac.uk>
Sent: 09 September 2023 19:55
To: dune-devel at lists.dune-project.org <dune-devel at lists.dune-project.org>
Subject: change to ci on branches?

Hi.
Has there been some change with the ci setup on branches recently?
The problem I'm encountering is that the ci is not trying to check out companion branches
on other modules aymore. So I have a branch (in  dune-fem and dune-grid in this case) with the same name and previously those were tested together. in the ci for dune-fem.

I check for example in an older pipeline in dune-grid  https://gitlab.dune-project.org/core/dune-grid/-/jobs/505888. On line 26-28:
Cloning into 'dune-common'...
error: pathspec 'feature/remove-deprecated-code' did not match any file(s) known to git
Parallel run with 4 processes

If I look at newer pipelines this 'error' does not come up anymore.
The first pipeline in dune-grid without that line is https://gitlab.dune-project.org/core/dune-grid/-/jobs/507666. Lines 24-26:
Cloning into 'dune-common'...
Parallel run with 4 processes

So the 'error' is missing and I guess that means that the ci is not trying to checkout a possibly companion branch. Those 2 pipelines are both tagged as 1 month ago.

I'm not sure where to look for this...
Hope everyone is well
Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20230922/566520ac/attachment.htm>