Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

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

已關閉
#1,735 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

已經有一個關聯 PR 被合併了。

  • #1809 來自 @fglock —— 已合併

評估

難度
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
平均合併
5 小時 39 分鐘
30 天內合併 PR
213

環境準備

  • 提供 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 摘要。