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

Nightly Windows: 3 Go workspace unit tests fail (Unix-only GOWORK paths)

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

維護者通常 1 天內回覆

@mikolalysenko 已經在處理了。

開始於 2026年10月29日。

  • #1816 來自 @mikolalysenko —— 未關閉

評估

難度
3/5
預估耗時
1-2 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
停滯
技術堆疊
github-actions, go, rust

研究方向

Read the failing tests in go_workspace.rs at lines 1141 and 1479 and golang.rs at line 1848, then inspect the Windows nightly run linked in the issue. Run the affected tests on Windows through the CI workflow_dispatch path. Done means all three assertions pass on Windows; issue #1816 is already an open pull request against this work.

由索引模型根據 Issue 內容生成。

描述

agent:claimed agent:triaged ci-janitor priority:p3

Nightly CI on main (run 40824880386, job test (windows-latest, 1)) fails -p socket-patch-core --lib with 3 of 6536 tests failing. These are deterministic assertion failures, not flakes. They came in with #1763 / #1764 (merged 2026-10-28). PR CI and the merge queue don't run the Windows test matrix, so the queue never saw them.

vendor::go_workspace::tests::gowork_resolves_as_go_does  (go_workspace.rs:1141)
  left:  Invalid("GOWORK=/elsewhere/go.work is not an absolute path, so go refuses to build …")
  right: File("/elsewhere/go.work")

vex::discover::golang::tests::gowork_naming_another_workspace_attests_nothing  (golang.rs:1848)
  /nonexistent/go.work: [Diag { code: "patched_ref_invalid", … GOWORK=/nonexistent/go.work is not an absolute path … }]

vendor::go_workspace::tests::a_workspace_module_is_never_replaced  (go_workspace.rs:1479)
  MainModule { work_file: "\\\\?\\C:\\Users\\runneradmin\\AppData\\Local\\Temp\\.tmpSk8aez\\ws\\go.work", member: "\\\\?\\C:\\…\\ws\\dep" }

Likely fix (test side): build the GOWORK fixtures from a tempdir or another absolute path that works on each platform instead of /elsewhere and /nonexistent. For the third test, compare paths after stripping the verbatim prefix (or canonicalize both sides), or find out where \\?\ comes from (a canonicalize on Windows). Open PRs #1812 and #1800 touch both files, so the janitor didn't change them this run. Whoever lands next should check these tests on Windows (workflow_dispatch of CI).

The cargo-home half of the same nightly failure is fixed in #1814.

主要語言
Rust
星號
8
分支
2
平均合併
19 小時 31 分鐘
30 天內合併 PR
686

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

SocketDev/socket-patch 的其他 Issue

查看 SocketDev/socket-patch 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。