Re: Solaris tar issues, or other reason why margay fails 010_pg_basebackup?
Thank you tom. SKIP_READLINE_TESTS works. margay is now green again. Best regards, Marcel Am 17.04.2024 um 21:12 schrieb Tom Lane: Thomas Munro writes: This test suite is passing on pollock because it doesn't have IO::Pty installed. Could you try uninstalling that perl package for now, so we can see what breaks next? If that's inconvenient for some reason, you could also skip the tab-completion test by setting SKIP_READLINE_TESTS in the animal's build_env options. regards, tom lane
Re: Solaris tar issues, or other reason why margay fails 010_pg_basebackup?
Hi Thomas Using gnu tar helps to make pg_basebackup work. It fails now at a later step. Best regards, Marcel Am 17.04.2024 um 10:52 schrieb Thomas Munro: On Wed, Apr 17, 2024 at 7:17 PM Marcel Hofstetter wrote: Is there a way to configure which tar to use? gnu tar would be available. -bash-5.1$ ls -l /usr/gnu/bin/tar -r-xr-xr-x 1 root bin 1226248 Jul 1 2022 /usr/gnu/bin/tar Cool. I guess you could fix the test either by setting TAR=/usr/gnu/bin/tar or PATH=/usr/gnu/bin:$PATH. If we want to understand *why* it doesn't work, someone would need to dig into that. It's possible that PostgreSQL is using some GNU extension (if so, apparently the BSDs' tar is OK with it too, and I guess AIX's and HP-UX's was too in the recent times before we dropped those OSes). I vaguely recall (maybe 20 years ago, time flies) that Solaris tar wasn't able to extract some tarballs but I can't remember why... I'm also happy to leave it at "Sun's tar doesn't work for us, we don't know why" if you are.
Re: Solaris tar issues, or other reason why margay fails 010_pg_basebackup?
Hi Is there a way to configure which tar to use? gnu tar would be available. -bash-5.1$ ls -l /usr/gnu/bin/tar -r-xr-xr-x 1 root bin 1226248 Jul 1 2022 /usr/gnu/bin/tar Which tar file is used? I could try to untar manually to see what happens. Best regards, Marcel Am 17.04.2024 um 06:21 schrieb Thomas Munro: Hi, I noticed that margay (Solaris) has started running more of the tests lately, but is failing in pg_basebaseup/010_pg_basebackup. It runs successfully on wrasse (in older branches, Solaris 11.3 is desupported in 17/master), and also on pollock (illumos, forked from common ancestor Solaris 10 while it was open source). Hmm, wrasse is using "/opt/csw/bin/gtar xf ..." and pollock is using "/usr/gnu/bin/tar xf ...", while margay is using "/usr/bin/tar xf ...". The tar command is indicating success (it's run by system_or_bail and it's not bailing), but the replica doesn't want to come up: pg_ctl: directory "/home/marcel/build-farm-15/buildroot/HEAD/pgsql.build/src/bin/pg_basebackup/tmp_check/t_010_pg_basebackup_replica_data/pgdata" is not a database cluster directory" So one idea would be that our tar format is incompatible with Sun tar in some way that corrupts the output, or there is some still difference in the nesting of the directory structure it creates, or something like that. I wonder if this is already common knowledge in the repressed memories of this list, but I couldn't find anything specific. I'd be curious to know why exactly, if so (in terms of POSIX conformance etc, who is doing something wrong).
Re: margay fails assertion in stats/dsa/dsm code
Am 28.06.2022 um 08:27 schrieb Thomas Munro:
On Fri, Jun 3, 2022 at 12:05 PM Thomas Munro wrote:
BF animal margay (a newly started Solaris 11.4/Sparc/GCC 11.2 box) is
sometimes failing with:
TRAP: FailedAssertion("seg->mapped_address != NULL", File: "dsm.c",
Line: 1069, PID: 9038)
I spent some time on the GCC farm machine gcc211 (Sol 11.3, GCC 5.5),
but could not repro this. It's also not happening on wrasse (Sol
11.3, Sun Studio compiler). I don't have access to a Sol 11.4
CBE/Sparc system like margay, but I have learned that CBE is the name
of a very recently announced rolling release intended for open source
developers[1]. I still have no idea if the active thing here is
Sparc, Sol 11.4, "CBE", GCC 11.2 or just timing conditions that reveal
bugs in our dsm/dsa/dshash/pgstat code that show up here in about 1/4
of make check runs on this stack, but miraculously nowhere else.
Perhaps margay's owner could shed some light, or has a way to provide
ssh access to a similar zone with a debugger etc installed?
[1]
https://blogs.oracle.com/solaris/post/announcing-the-first-oracle-solaris-114-cbe
Looks like a timing issue for me, because it happens only sometimes.
No problems with versions 14 and 13.
I can provide ssh access to this system.
