On Wed, Mar 23, 2022 at 12:44:09PM +1300, Thomas Munro wrote:
> On Mon, Mar 21, 2022 at 12:46 PM Thomas Munro wrote:
> > On Mon, Mar 21, 2022 at 12:23 PM Thomas Munro
> > wrote:
> > > On Mon, Mar 21, 2022 at 1:58 AM Matthias van de Meent
> > > wrote:
> > > > Additionally, are there plans to va
On Mon, Mar 21, 2022 at 12:46 PM Thomas Munro wrote:
> On Mon, Mar 21, 2022 at 12:23 PM Thomas Munro wrote:
> > On Mon, Mar 21, 2022 at 1:58 AM Matthias van de Meent
> > wrote:
> > > Additionally, are there plans to validate commits of the main branch
> > > before using them as a base for CF ent
On Mon, Mar 21, 2022 at 3:11 PM Andres Freund wrote:
> On 2022-03-21 14:44:55 +1300, Thomas Munro wrote:
> > Those tooltips come from the "name" elements of the .cirrus.yml file
> > where tasks are defined, with Cirrus's task status appended. If we
> > had a set of monochrome green and red icons
Hi,
On 2022-03-21 14:44:55 +1300, Thomas Munro wrote:
> Those tooltips come from the "name" elements of the .cirrus.yml file
> where tasks are defined, with Cirrus's task status appended. If we
> had a set of monochrome green and red icons with a Linux penguin,
> FreeBSD daemon, Windows logo and
On Sun, Mar 20, 2022 at 6:45 PM Thomas Munro wrote:
> Nice idea, if someone with graphics skills is interested in looking into it...
The logo thing wasn't really the point for me. I'd just like to have
the information be more visible, sooner.
I was hoping that there might be a very simple method
On Mon, Mar 21, 2022 at 1:41 PM Peter Geoghegan wrote:
> BTW, I think that the usability of the CFBot website would be improved
> if there was a better visual indicator of what each "green tick inside
> a circle" link actually indicates -- what are we testing for each
> green tick/red X shown?
>
>
On Sun, Mar 20, 2022 at 4:23 PM Thomas Munro wrote:
> On Mon, Mar 21, 2022 at 1:58 AM Matthias van de Meent
> wrote:
> > Would you know how long the expected bitrot re-check period for CF
> > entries that haven't been updated is, or could the bitrot-checking
> > queue be displayed somewhere to in
Hi,
On 2022-03-21 12:23:02 +1300, Thomas Munro wrote:
> or actually a shade fewer because it's pretty dumb and only wakes up once a
> minute to decide what to do
Might be worth using https://cirrus-ci.org/api/#webhooks to trigger a run of
the scheduler. Probably still want to have the timeout bas
Hi,
On 2022-03-21 12:23:02 +1300, Thomas Munro wrote:
> It was set to try to recheck every ~48 hours, though it couldn't quite
> always achieve that when the total number of eligible submissions is
> too large. In this case it had stalled for too long after the github
> outage, which I'm going to
On Mon, Mar 21, 2022 at 12:23 PM Thomas Munro wrote:
> On Mon, Mar 21, 2022 at 1:58 AM Matthias van de Meent
> wrote:
> > Would you know how long the expected bitrot re-check period for CF
> > entries that haven't been updated is, or could the bitrot-checking
> > queue be displayed somewhere to i
On Mon, Mar 21, 2022 at 1:58 AM Matthias van de Meent
wrote:
> Would you know how long the expected bitrot re-check period for CF
> entries that haven't been updated is, or could the bitrot-checking
> queue be displayed somewhere to indicate the position of a patch in
> this queue?
I see that you
On Sun, Mar 20, 2022 at 01:58:01PM +0100, Matthias van de Meent wrote:
>
> I noticed that two of my patches (37/3543 and 37/3542) both failed due
> to a bad commit on master (076f4d9). The issue was fixed an hour later
> with b61e6214; but the pipeline for these patches hasn't run since.
> Because
On Fri, 18 Mar 2022 at 19:52, Thomas Munro wrote:
> 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...
I noticed that two of
>
> confused Cirrus. 🤷 There is already another build for 3489 that is
> almost finished now so I don't think that stale TRIGGERED one is
> stopping anything from working and I guess it will eventually go away
> by itself somehow...
>
Indeed, I saw this now. No problem anymore.
Thanks!
--
Best r
On Sat, Mar 19, 2022 at 9:41 AM Pavel Borisov wrote:
>>
>> 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:postgres
>
> 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'
>
I am seeing commitfest/37/3489 in
On Sat, Mar 19, 2022 at 5:07 AM Julien Rouhaud 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,
Hi,
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.
>
18 matches
Mail list logo
