On Fri, Apr 3, 2020 at 9:52 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: > > 'prairiedog' is also unhappy, and it looks related: > > Yeah, gaur also failed in the same place. Both of those are > alignment-picky 32-bit hardware, so I'm thinking the problem is > pg_gmtime() trying to fetch a 64-bit pg_time_t from an insufficiently > aligned address. I'm trying to confirm that on gaur's host right now, > but it's a slow machine ...
You might just want to wait until tomorrow and see whether it clears up in newer runs. I just pushed yet another fix that might be relevant. 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. I apologize to everyone who has been or will be inconvenienced by all of this. So far I've pushed 4 test case fixes, 2 bug fixes, and 1 makefile fix, which I'm pretty sure is over quota for one patch. :-( -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
