Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Handle IPC::Run tests that require unsupported fork()

未关闭
#1,735 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
java, perl
领域
testing

调研方向

Start with the process-launching implementation used by IPC::Run and the tests for Pod::HtmlEasy, especially t/bugs.t and t/options.t. Reproduce with timeout 1800 ./jcpan -t Pod::HtmlEasy, then determine where unsupported fork() calls are detected and how test outcomes are reported. Done means these tests either complete through a supported process implementation or are consistently marked as requiring unsupported fork().

由索引模型根据 Issue 内容生成。

描述

Problem

PerlOnJava does not implement fork(). CPAN distributions whose test harnesses rely on IPC::Run can therefore have every assertion pass while their test programs still exit unsuccessfully. This currently affects Pod::HtmlEasy: t/bugs.t and t/options.t report all assertions passing, then the jcpan -t Pod::HtmlEasy run exits 8 when IPC::Run attempts to fork.

Expected behavior

Tests that use IPC::Run should either run successfully with a supported process implementation or be reported and handled consistently as tests that require unsupported fork().

Reproduction

timeout 1800 ./jcpan -t Pod::HtmlEasy

Observed: 82 assertions pass, but two test programs fail to complete because fork() is unavailable.

Related: #1662 and draft PR #1734. This is a separate follow-up from the Errno import fix so it remains tracked when #1662 closes.

主要语言
Perl
星标
64
派生
7
平均合并
4 小时 57 分钟
30 天内合并 PR
203

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fglock/PerlOnJava 的其他 Issue

查看 fglock/PerlOnJava 的全部 Issue

相似的 Issue

更多 Perl Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。