From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Probable CF bot degradation |
Date: | 2022-03-18 18:51:43 |
Message-ID: | CA+hUKGLL1gB+DbyZT7Ec3h3cDyFvONktThUSn_E3QPcR_K69Rw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 19, 2022 at 5:07 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> On Fri, Mar 18, 2022 at 07:43:47PM +0400, Pavel Borisov wrote:
> > Hi, hackers!
> > I've noticed that CF bot hasn't been running active branches from yesterday:
> > https://github.com/postgresql-cfbot/postgresql/branches/active
> >
> > Also, there is no new results on the current CF page on cputube.
> > I don't know if it is a problem or kind of scheduled maintenance though.
>
> There was a github incident yesterday, that was resolved a few hours ago ([1]),
> maybe the cfbot didn't like that.
Yeah, for a while it was seeing:
remote: Internal Server Error
To github.com:postgresql-cfbot/postgresql.git
! [remote rejected] commitfest/37/3489 -> commitfest/37/3489
(Internal Server Error)
error: failed to push some refs to 'github.com:postgresql-cfbot/postgresql.git'
Unfortunately cfbot didn't handle that failure very well and it was
waiting for a long timeout before scheduling more jobs. It's going
again now, and I'll try to make it more resilient against that type of
failure...
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Borisov | 2022-03-18 18:52:02 | Fix unsigned output for signed values in SLRU error reporting |
Previous Message | Imseih (AWS), Sami | 2022-03-18 17:32:45 | Re: [PATCH] pgbench: add multiconnect option |