Skip to content

Make CPAN random tester safe for parallel runs #863

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fglock merged 1 commit into from
Jun 18, 2026
Merged

Make CPAN random tester safe for parallel runs #863

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion dev/cpan-reports/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,9 @@ PerlOnJava (`jcpan`). The data is used to:

The `.dat` files are updated by the automated CPAN tester
(`dev/tools/cpan_random_tester.pl` or similar). Do not edit them by hand
unless correcting an obvious error — they are append-only logs.
unless correcting an obvious error. The random tester serializes report
updates with a lock, reloads current state before writing, and rewrites the
files atomically so multiple tester instances can safely run at once.

When a module's status changes (e.g. newly passing after a fix), update the
corresponding per-module `.md` note as well.
Expand Down
6 changes: 3 additions & 3 deletions dev/prompts/cpan-compatibility-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ perl dev/tools/cpan_random_tester.pl --report-only

5. **Git commit tracking**: Every PASS records the git commit hash. If a future run detects a PASS→FAIL regression, you can bisect between the known-good commit and HEAD.

6. **Crash-safe persistence**: Results are saved to `.dat` files after each target module, so partial runs are never lost.
6. **Incremental/concurrent persistence**: Results are saved after each target. Shared report writes are lock-protected, merged with the latest `.dat` state, and replaced atomically so parallel tester instances do not drop each other's results.

7. **Report**: A Markdown report is generated at `dev/cpan-reports/cpan-compatibility.md`.

Expand All @@ -55,7 +55,7 @@ perl dev/tools/cpan_random_tester.pl --report-only
| `dev/cpan-reports/cpan-compatibility-pass.dat` | Pass list (TSV, includes git commit) |
| `dev/cpan-reports/cpan-compatibility-fail.dat` | Fail list (TSV) |
| `dev/cpan-reports/cpan-compatibility-skip.dat` | Skip list (TSV) |
| `/tmp/cpan_random_logs/` | Per-module test output logs |
| `/tmp/cpan_random_logs/<Run-ID>/` | Per-module test output logs |

## Workflow for Growing the Report

Expand Down Expand Up @@ -124,5 +124,5 @@ When a module transitions from PASS to FAIL:
- Run with `perl` (not `jperl`) since the script uses `fork` and backticks.
- The CPAN index must exist at `~/.cpan/sources/modules/02packages.details.txt.gz`. Run `./jcpan` once interactively if it's missing.
- Use `--seed N` for reproducible random selection.
- Logs for individual modules are in `/tmp/cpan_random_logs/<Module-Name>.log`.
- Logs for individual modules are in `/tmp/cpan_random_logs/<Run-ID>/<Module-Name>.log`.
- The existing `dev/tools/cpan_smoke_test.pl` tests a curated list of known modules. This script complements it by discovering new compatible modules from the full CPAN index.
Loading
Loading