On Fri, Apr 3, 2020 at 10:43 PM Robert Haas <robertmhaas@gmail.com> wrote:
> I think I've done about as much as I can do for tonight, though. Most
> things are green now, and the ones that aren't are failing because of
> stuff that is at least plausibly fixed. By morning it should be
> clearer how much broken stuff is left, although that will be somewhat
> complicated by at least sidewinder and seawasp needing manual
> intervention to get back on track.
Taking stock of the situation this morning, most of the buildfarm is
now green. There are three failures, on eelpout (6 hours ago),
fairywren (17 hours ago), and hyrax (3 days, 7 hours ago).
eelpout is unhappy because:
+WARNING: could not remove shared memory segment
"/PostgreSQL.248989127": No such file or directory
+WARNING: could not remove shared memory segment
"/PostgreSQL.1450751626": No such file or directory
multibatch
------------
f
@@ -861,22 +863,15 @@
select length(max(s.t))
from wide left join (select id, coalesce(t, '') || '' as t from wide)
s using (id);
- length
---------
- 320000
-(1 row)
-
+ERROR: could not open shared memory segment "/PostgreSQL.605707657":
No such file or directory
+CONTEXT: parallel worker
I'm not sure what caused that exactly, but it sorta looks like
operator intervention. Thomas, any ideas?
fairywren's last run was on 21dc488, and commit
460314db08e8688e1a54a0a26657941e058e45c5 was an attempt to fix what
broken there. I guess we'll find out whether that worked the next time
it runs.
hyrax's last run was before any of this happened, so it seems to have
an unrelated problem. The last two runs, three and six days ago, both
failed like this:
-ERROR: stack depth limit exceeded
+ERROR: stack depth limit exceeded at character 8
Not sure what that's about.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
