| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Georgios <gkokolatos(at)protonmail(dot)com> |
| Subject: | Re: Commitfest 2020-11 is closed |
| Date: | 2020-12-02 21:15:06 |
| Message-ID: | CA+hUKG+D=SOTVcYrsrQjELKzhyMubW2rv8Y-WJNvoUivrUH57w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 3, 2020 at 10:00 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This is actually a bit problematic, because now the cfbot is ignoring
> those patches (or if it's not, I don't know where it's displaying the
> results). Please go ahead and move the remaining open patches, or
> else re-open the CF if that's possible.
As of quite recently, Travis CI doesn't seem to like cfbot's rate of
build jobs. Recently it's been taking a very long time to post
results for new patches and taking so long to get around to retesting
patches for bitrot that the my "delete old results after a week" logic
started wiping out some results while they are still the most recent,
leading to the blank spaces where the results are supposed to be.
D'oh. I'm looking into a couple of options.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-12-02 21:23:20 | Re: libpq compression |
| Previous Message | Tom Lane | 2020-12-02 20:59:51 | Re: Commitfest 2020-11 is closed |