perl-test-sharedfork

Build times (auto-updated)

• any: 51s (2026-11-01 09:48 UTC, MAKEFLAGS=-j6)

---

• Path: arch/maintained/perl-test-sharedfork (new – vendored from AUR 2026-08-02, transitive checkdepends of perl-filesys-notify-simple -> perl-plack -> thruk). Its dependency perl-test-requires was already in official extra.
• 2026-08-02: built+published cleanly (0.35-2), any package.
• No longer an actual arch/maintained/ submodule, but still bucketed under the maintained/ category in scripts/install_only_packages (see [[perl-filesys-notify-simple]] for the same note).
• 2026-10-29: perl-5.44 ABI rebuild batch (see [[mtop]]), same 0.35-2, clean. Note: the freshly-republished copy of this exact package then caused a transient pacman “corrupted package (checksum)” failure for [[perl-test-tcp]] a few minutes later in the same session, when perl-test-tcp’s build tried to pull this package as a dependency from the repo mirror right after the republish – looked like a mirror-propagation race, not a real content problem (a plain retry of perl-test-tcp worked). Worth remembering if a sibling package’s build fails on a checksum error for a package rebuilt moments earlier in the same batch.
• 2026-11-01: another perl-ABI batch. Bumped pkgrel 2 -> 2.1 (X.Y, content-free rebuild), built+published cleanly at 0.35-2.1. Built this one before [[perl-test-tcp]] in the same batch this time (its dependency), to avoid repeating the mirror-propagation race noted above. check()’s log shows Failed test 'child three'/Failed test 'foo' lines – harmless, not a real failure: t/10_subtest.t and t/12_is_passing.t are meta-tests that deliberately simulate failing sub-tests to exercise Test::SharedFork’s own failure-reporting; the outer harness correctly marks both ok and the final summary says “All tests successful.” A plain -i grep for FAILED will match these lines (lowercase “Failed”) – don’t mistake them for a real check() regression.