Skip to content

fix: cap cpan_random_tester at 90 minutes and clean up our JVMs#850

Merged
fglock merged 1 commit into
masterfrom
fix/cpan-random-tester-90min-cap
Jun 9, 2026
Merged

fix: cap cpan_random_tester at 90 minutes and clean up our JVMs#850
fglock merged 1 commit into
masterfrom
fix/cpan-random-tester-90min-cap

Conversation

@fglock

@fglock fglock commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Summary

  • Default --max-runtime to 5400 seconds (90 minutes) per target module so chatty jcpan installs/tests cannot run for many hours regardless of output activity
  • On timeout, clean up stray PerlOnJava JVMs that escaped the jcpan process group (e.g. parallel prove --jobs workers) by killing only PIDs tracked as descendants of our forked jcpan child — unrelated user jperl runs are left alone
  • Cap per-module soft timeouts at --max-runtime; document --max-runtime 0 to disable the hard cap

Test plan

  • perl -c dev/tools/cpan_random_tester.pl
  • Run perl dev/tools/cpan_random_tester.pl --modules Some::Small::Module --timeout 30 and confirm normal completion
  • Run with --max-runtime 60 --timeout 10 on a slow module and confirm timeout + no orphan JVMs from that run

Made with Cursor

Default --max-runtime to 5400s so chatty jcpan installs cannot run for
many hours. On timeout, kill only perlonjava JVMs tracked as descendants
of the forked jcpan child so unrelated user jperl processes are untouched.

Generated with [Cursor](https://cursor.com)

Co-Authored-By: Cursor <cursoragent@cursor.com>
@fglock fglock merged commit 7fbc52e into master Jun 9, 2026
2 checks passed
@fglock fglock deleted the fix/cpan-random-tester-90min-cap branch June 9, 2026 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant