Re: Allow CI to only run the compiler warnings task

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Allow CI to only run the compiler warnings task
Date: 2024-09-12 05:21:43
Message-ID: ZuJ6Z6fP31GgHohh@ip-10-97-1-34.eu-west-3.compute.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Wed, Sep 11, 2024 at 04:39:57PM +0300, Nazir Bilal Yavuz wrote:
> Hi,
>
> On Wed, 11 Sept 2024 at 15:36, Bertrand Drouvot
> <bertranddrouvot(dot)pg(at)gmail(dot)com> wrote:
> >
> > Hi hackers,
> >
> > While working on a new pg_logicalinspect module ([1]), I reached a point where
> > all the CI tests were green except the compiler warnings one. Then, to save time
> > addressing the issue, I modified the .cirrus.tasks.yml file to $SUBJECT.
> >
> > I think this could be useful for others too, so please find attached this tiny
> > patch.
>
> +1 for this. I encountered the same issue before.

Thanks for the feedback!

>
> > Note that the patch does not add an extra "ci-task-only", but for simplicity it
> > it renames ci-os-only to ci-task-only.
>
> I think this change makes sense. I gave a quick try to your patch with
> ci-task-only: ["", "linux", "compilerwarnings"] and it worked as
> expected.

And for the testing.

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2024-09-12 05:30:23 Re: Pgoutput not capturing the generated columns
Previous Message Michael Paquier 2024-09-12 05:18:35 Re: Avoid dead code (contrib/pg_visibility/pg_visibility.c)