| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Intermittent buildfarm failures on wrasse |
| Date: | 2022-04-15 03:56:15 |
| Message-ID: | 1583505.1649994975@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> One thing I'm eyeing now is that it looks like Noah is re-initdb'ing
> each time, whereas I'd just stopped and started the postmaster of
> an existing installation. That does not seem like it could matter
> but ...
Well, damn. I changed my script that way and it failed on the tenth
iteration (versus a couple hundred successful iterations the other
way). So somehow this is related to time-since-initdb, not
time-since-postmaster-start. Any ideas?
Anyway, I'm too tired to do more tonight, but now that I can reproduce it
I will stick some debugging logic in tomorrow. I no longer think we
should clutter the git repo with any more short-term hacks.
regards, tom lane
PS a bit later: I've not yet reproduced it a second time, so the
failure rate is unfortunately a lot less than one-in-ten. Still,
this eliminates the idea that there's some secret sauce in Noah's
build details.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-04-15 04:50:27 | Re: Intermittent buildfarm failures on wrasse |
| Previous Message | Noah Misch | 2022-04-15 03:27:09 | Re: Intermittent buildfarm failures on wrasse |