PETSc devs using CI@gitlab, One of the CI builds is failing - and the fix for it is now in latest maint/master [as of now].
All new test pipelines require this fix to succeed. So please rebase your branch [over maint or master - as appropriate] before submitting any new test pipelines. i.e: git checkout feature-branch git fetch git rebase origin/master [or origin/maint] # Note: do not skip 'origin/' as listed here If the feature branch is not rebased - it will be stuck at stage-2 job arch-ci-linux-gcc-complex-opt. To verify if a feature-branch has this fix - check with: git branch --contains c0dad76995 feature-branch Satish On Thu, 30 Jan 2020, Satish Balay via petsc-dev wrote: > To clarify: > > CI uses .gitlab-ci.yaml from the branch - and not the latest from > maint/master - so if your branch has old version of this file, and start > a pipeline on it - it will get stuck - and timeout. > > To determine if your branch has this .gitlab-ci.yaml change [requiring > a rebase] - see if it has the commit: > > git branch --contains 0b416d8e105a765da5769e4b7feab5986dc829a2 > > Satish > > On Wed, 29 Jan 2020, Balay, Satish via petsc-dev wrote: > > > PETSc devs using CI@gitlab, > > > > With the current CI changes - before starting a test pipeline on a > > branch at gitlab, its best to rebase the branch over current master as > > of now [or maint - if appropriate]. > > > > If a test pipeline is created with non-rebased branch, some of the > > stage-2 jobs will be stuck - so the pipeline won't complete. > > > > Satish > > >
