Dist::Zilla release archive disappears before release plugins consume it
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 58/100
Rechercherichtung
Start by running prove -v t/plugins/testrelease.t t/plugins/uploadtocpan.t t/tester.t under PerlOnJava and compare the archive lifecycle with standard Perl. Trace the release entry point and the consumers named in those tests, especially the tester's source archive path. Done means the archive remains available through TestRelease and UploadToCPAN, and all three focused tests pass.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Summary
PerlOnJava loses a Dist::Zilla release archive before release plugins can consume it. The same missing archive causes three otherwise independent upstream tests to fail:
t/plugins/testrelease.tcannot extractDZT-Sample-0.001.tar.gzduringTestRelease.t/plugins/uploadtocpan.tnever reportsUploading ... DZT-Sample, because its fake uploader sees that the archive path is not a file.t/tester.tdies before producing a TAP plan whenArchive::Tar->newis given the absent archive.
The error from TestRelease is Could not open ... DZT-Sample-0.001.tar.gz for reading: No such file or directory.
Oracle and impact
CPAN random run 20260924-115230-59978 tested Dist::Zilla 6.039. The unmodified upstream suite passes under isolated standard Perl 5.42.2: 57 files and 504 tests, Result: PASS.
Under the PerlOnJava JVM backend, the acceptance run fails 38 of 531 subtests across 5 files. This archive-lifecycle cluster accounts for the failures in the three files above. Dist::Zilla is pure Perl, so native/XS support is not involved.
Focused reproducer
With Dist::Zilla's normal test prerequisites installed, run the upstream focused tests without modification:
prove -v t/plugins/testrelease.t t/plugins/uploadtocpan.t t/tester.t
Standard Perl passes all three. PerlOnJava fails them after release because the archive expected at the tester's source path is gone.
The essence of the upstream t/tester.t reproducer is:
use Test::DZil;
use Archive::Tar;
my $tzil = Builder->from_config(
{ dist_root => 'corpus/dist/DZT' },
{ add_files => {
'source/zero' => '',
'source/dist.ini' => simple_ini({ name => 'DZT' }, 'GatherDir', 'MakeMaker', 'FakeRelease'),
} },
);
$tzil->release;
my $archive = $tzil->built_in->parent->child('source')->child($tzil->archive_filename);
die "archive missing: $archive\n" unless -f $archive;
Archive::Tar->new("$archive");
Expected behavior
The archive produced by release must remain present until the TestRelease and UploadToCPAN consumers have processed it, matching standard Perl and Dist::Zilla's upstream lifecycle.
Duplicate search
No existing issue matched Dist::Zilla archive handling, DZT-Sample, TestRelease, or UploadToCPAN at filing time. Issue #1508 concerns the already-fixed TrialVersionComment plugin and is unrelated.
- Vorherrschende Sprache
- Perl
- Sterne
- 64
- Forks
- 6
- Ø Merge
- 4 Std. 42 Min.
- Gemergte PRs (30 T.)
- 182
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus fglock/PerlOnJava
-
area:cpan-port area:unicode bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
fglock/PerlOnJava#1341 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:cpan-port area:regex area:unicode bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 52/100
fglock/PerlOnJava#1556 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:backend area:runtime bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
fglock/PerlOnJava#1554 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:cpan-port area:runtime bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 55/100
fglock/PerlOnJava#1552 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:backend area:cpan-port bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
fglock/PerlOnJava#1548 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in fglock/PerlOnJava
Ähnliche Issues
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 87/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
objectionary/eolang.sty#184 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
linux-test-project/lcov#542 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100