cfbot failures

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: cfbot failures
Date: 2023-02-20 01:08:41
Message-ID: 20230220010841.GK1653@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-02-11, Andres Freund wrote 20230212004254(dot)3lp22a7bpkcjo3y6(at)awork3(dot)anarazel(dot)de:
> The windows test failure is a transient issue independent of the patch
> (something went wrong with image permissions).

That's happening again since 3h ago.
https://cirrus-ci.com/github/postgresql-cfbot/postgresql

I suggested in the past that cfbot should delay if (say) the last 5 or
10 consecutive runs all failed (or maybe all failed on the same "task").

Maybe that should only apply to re-tests but not to new patches. It
could inject 15min delays until the condition is resolved. Or it could
run retests on a longer interval like 96h instead of 24. And add a
warning or start beeping about the issue.

That would mitigate not only issues in the master branch but also issues
with CI infrastructure (cirrus/google/images).

--
Justin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-02-20 01:18:28 Re: cfbot failures
Previous Message Thomas Munro 2023-02-19 23:28:54 Re: windows CI failing PMSignalState->PMChildFlags[slot] == PM_CHILD_ASSIGNED