Nightly Windows: 3 Go workspace unit tests fail (Unix-only GOWORK paths)
维护者通常 1 天内回复
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 35/100
调研方向
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 内容生成。
描述
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 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
SocketDev/socket-patch 的其他 Issue
-
bug bughunt pm:npm
难度 4/5 3-5 天 新手友好度 53/100
SocketDev/socket-patch#1827 · 1 条评论 ·
维护者通常 1 天内回复
-
Go apply, apply --check and vex treat a module that is only another module's replace target as built, so the patch is reported applied and attested while go builds the unpatched code可能已有人在做 @mikolalysenko 今天认领。 未关闭agent:claimed agent:triaged bug bughunt pm:go priority:p2
难度 4/5 3-5 天 新手友好度 48/100
SocketDev/socket-patch#1823 · 3 条评论 ·
维护者通常 1 天内回复
-
Vendored gem mode writes the rewired `gem` line of a CRLF Gemfile with an LF ending, leaving the Gemfile with mixed line endings可能已有人在做 @mikolalysenko 今天认领。 未关闭agent:claimed agent:triaged bug bughunt pm:bundler priority:p1
难度 3/5 1-2 天 新手友好度 25/100
SocketDev/socket-patch#1821 · 3 条评论 ·
维护者通常 1 天内回复
-
CI perf: workflow_dispatch of CI — Windows-only janitor fixes re-run the full Linux + macOS nightly matrix (~100 min/day, ~30 macOS)可能已有人在做 @mikolalysenko 今天认领。 未关闭agent:claimed agent:triaged ci-perf priority:p3
难度 4/5 3-5 天 新手友好度 1/100
SocketDev/socket-patch#1818 · 3 条评论 ·
维护者通常 1 天内回复
-
Go apply writes the shared replace into ./go.work when GOWORK names another file in the same directory, reports success, and the workspace builds unpatched可能已有人在做 @mikolalysenko 于 1 天前认领。 未关闭agent:claimed agent:triaged bug bughunt pm:go priority:p2
难度 4/5 1-2 天 新手友好度 35/100
SocketDev/socket-patch#1810 · 3 条评论 ·
维护者通常 1 天内回复
查看 SocketDev/socket-patch 的全部 Issue
相似的 Issue
-
priority middle
难度 1/5 1 小时以内 新手友好度 62/100
KATO-Hiro/AtCoderClans#12940 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
o8 next debug build aborts on Glass to Dark appearance switch (nil identifier messaged before check)未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
hurttlocker/o8#5112 ·
-
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复