On Tue, Nov 07, 2023 at 11:41:21PM +0200, Francis Laniel wrote: > The CI can fails previously for reasons which are not tied to hush 2021. > Let's build the world in any case to check everything is OK there too. > > Signed-off-by: Francis Laniel <francis.lan...@amarulasolutions.com> > --- > .azure-pipelines.yml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml > index d6f3fa423c..4eaf0e9062 100644 > --- a/.azure-pipelines.yml > +++ b/.azure-pipelines.yml > @@ -469,6 +469,7 @@ stages: > retryCountOnTaskFailure: 2 # QEMU may be too slow, etc. > > - stage: world_build > + condition: always() > jobs: > - job: build_the_world > timeoutInMinutes: 0 # Use the maximum allowed
I _think_ this patch can just be dropped from your series as well at this point. Azure now has some automatic retry logic that catches most of the cases of when the job fails but it's not our codebase that caused the problem and it's something transient to the CI hosts/etc. -- Tom
signature.asc
Description: PGP signature
