Re: Having trouble serializing test with Automake parallel test harness

"G. Branden Robinson" <[email protected]> Mon, 22 Jun 2026 16:32:39 -0500
Newsgroups gmane.comp.printing.groff.general,gmane.comp.sysutils.automake.general
Message-ID <20260622213239.t76lq4b3pes5pjmp@illithid>
--jyu6vvz74xgkma22
Content-Type: text/plain; protected-headers=v1; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Re: Having trouble serializing test with Automake parallel test
 harness
MIME-Version: 1.0

Hi Karl,

At 2026-06-22T08:25:43-0600, Karl Berry wrote:
> Hi Branden - returning to your question about serialization of Automake
> tests from March 5:
>=20
>     https://lists.gnu.org/archive/html/automake/2026-03/msg00000.html
>     ...
>     Was I using the documented serialization mechanism incorrectly?
>     Why didn't it work?
>=20
> I doubt it can be this simple, but maybe add .sh to TEST_EXTENSIONS?
> "Parallel Test Harness" has this (rather buried in the text) sentence:
>=20
>   https://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Ha=
rness.html
>   ...
>   please note that specifying such dependencies currently works only
>   for tests that end in one of the suffixes listed in
>   @code{TEST_EXTENSIONS}.
>=20
> When I look at the groff-1.24.1 tarball (what I had at hand), I see
>   ./Makefile.in:2738:TEST_EXTENSIONS =3D @EXEEXT@ .test
> but your tests are using .sh.

Yes.  I inherited the the test framework from the previous groff
maintainer, Bertrand Garrigues.

> If it still fails to serialize correctly (I won't be surprised), can
> you please try to make a small reproducible example? Debugging in
> something the size of groff is difficult.

I've resolved the problem by other means, per the below.

> P.S. Regarding core dumps, allow me to echo Bob F's comment: on some
> systems (at least, every RHEL system I've ever seen), core dumps are
> disabled by default. And it's not trivial to enable them. ulimit -c
> does not suffice. What happens to core dumps is determined by
> /proc/sys/kernel/core_pattern and on RHEL, that is set to
> |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %d %F and I
> gave up on figuring out what happens after that. Core files don't end
> up in the current directory, though, that's for sure.
>=20
> Bottom line, for reliable tests, I think you cannot rely on a core
> file being generated.

I've since removed all tests for core files.  That in turn eliminates
the need to impose an ordering on the test scripts.

https://savannah.gnu.org/bugs/?68204

Regards,
Branden

--jyu6vvz74xgkma22
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAmo5qfAACgkQ0Z6cfXEm
bc494Q//c0+0ErFtfujKPa7FRLnHikS9B8+lNHS5C5+/5NMnu1NkAf5D49wiQ2HX
f+zh2tOqXkwkxozLdHut67itJNkvVginuCBrDSkGPuq5+d8dEPMT6dnNRZPl5X4k
szzcdeH1UNuVwF6urxAh87RVpCfnjoqkRdBhzCyoMSGYLBximKcJ3+Kd2TbU7vkq
xpH8iqWBIrjikgdoNNcEj+gZqPPT9M1wcGqBBFlD8wHbVMdVf+ckjr4haakXdPJH
J8sxVwU3CfE24gp5l6BnCX7M1cbA2Flg7FtNXvDKubwufzpQUW5iEIo5uRNhbUVc
38lGjiyKQtg3+j5Wg8kjcSKZuLoiW5z7Jo/Rali9t2YIYbFvvyBkAKmqA3HyhDW5
hjVSM5fIXPBJljrgEnDgmKzr61yr0jhAhq3VmU5cwtcfC6tSnLz9S9R5sKeL4tDh
NGW6ANoP6xK5kP2QT2dt4inbbS8bsnKtuAPswsw4LGhx5hsX8/52SnI2VLqA0FiJ
4tBjiENiUD2arTZUfb9w7skA1VRH7qQ9cqtWhbyX1r0u8HPrgpBElSMwl1EXafCu
JZicKwY+6AZgbZjnIGH9XB/PKT6Hu6MPlPnNSB4nGxsV+UYkGESCkfkRgLwv2MMV
r+ATxlmz+vrdgrsbC6dPDR03MCU4oyAaGAIpK6pSFJu9PETjwl8=
=HG21
-----END PGP SIGNATURE-----

--jyu6vvz74xgkma22--