GEGL 0.4.30 FTBFS due spurious Meson TAP test failures seemingly due to older Python
GEGL 0.4.30 FTBFS due spurious Meson TAP test failures seemingly due to older Python, such as with pre-Focal (ie. Xenial and Bionic) Ubuntu releases. Six tests using TAP all fail even though they actually return "OK" (exit status 0):
30/249 gegl:simple / buffer_changes FAIL 0.27s (exit status 0)
31/249 gegl:simple / gegl_color FAIL 0.28s (exit status 0)
32/249 gegl:simple / gegl_tile FAIL 0.27s (exit status 0)
59/249 gegl:xml / test_load FAIL 0.37s (exit status 0)
60/249 gegl:xml / test_roundtrip FAIL 0.37s (exit status 0)
61/249 gegl:xml / test_save FAIL 0.37s (exit status 0)
Here's the excerpt from meson-logs/testlog.txt for one of the failures:
30/249 gegl:simple / buffer_changes FAIL 0.27s (exit status 0)
--- command ---
17:55:29 GEGL_SWAP='RAM' ABS_TOP_BUILDDIR='/build/gegl-0.4.30/obj-x86_64-linux-gnu' GEGL_PATH='/build/gegl-0.4.30/obj-x86_64-linux-gnu/operations' ABS_TOP_SRCDIR='/build/gegl-0.4.30' /build/gegl-0.4.30/obj-x86_64-linux-gnu/tests/simple/buffer-changes
--- stdout ---
/buffer/change/signal-on-set: OK
/buffer/change/no-signal-with-iter-read: OK
/buffer/change/signal-with-iter-readwrite: OK
/buffer/change/signal-with-iter-write: OK
--- stderr ---
TAP parsing error: unexpected input at line (1,)
TAP parsing error: unexpected input at line (2,)
TAP parsing error: unexpected input at line (3,)
TAP parsing error: unexpected input at line (4,)
-------
The attached patch fixes the issue for older Ubuntu versions (ie. Xenial and Bionic) allowing the build to succeed with all tests passing as expected. Maybe not a very important issue to fix, due only happening on older distributions, but reporting it here due the fact that this is a new FTBFS since GEGL 0.4.28 for at least some systems.