A test project passes with zero tests, and the CI shards are listed by hand
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
调研方向
Start with Directory.Build.props:73-76, .github/workflows/ci.yml:90-106, DatabaseServer.cs:90, and SqlServerPool.cs:32-45 to trace the test settings, shard coverage, and existing database template approach. Check how the solution discovers test projects and how PostgreSQL tests create and migrate databases. Done means empty test projects fail, every test project is covered by a shard, and PostgreSQL tests migrate once per run; record the time saved in the pull request. Coordinate with #3267, which changes the same workflow.
由索引模型根据 Issue 内容生成。
描述
Problem
- A test project passes when it runs no tests.
Directory.Build.props:73-76sets--ignore-exit-code 8for every project undertests/, with a comment about stubs that no longer applies. Filtered runs are guarded by--minimum-expected-tests; the unfiltered shards (.github/workflows/ci.yml:90,101-106) are not. - The shard lists are maintained by hand.
ci.yml:90-106names each test project. A new one runs on no pull request and no push to main; only the nightly Windows run picks it up. - PostgreSQL tests create and migrate a database per test.
DatabaseServer.cs:90runsCREATE DATABASEfor each test, and each test migrates it. SQL Server already clones a migrated template (SqlServerPool.cs:32-45).
Proposal
- Remove the ignored exit code.
- A check that every test project of the solution is in a shard.
- Migrate one template database per run and create test databases from it.
Done together with #3267, which changes the same workflow.
Acceptance
- A test project that discovers no tests fails the run
- A test project missing from the shards fails CI
- PostgreSQL tests no longer migrate per test; the time saved is noted in the pull request
Found in the code review of 17 Nov 2026.
- 主要语言
- C#
- 星标
- 569
- 派生
- 107
- 平均合并
- 2 小时 49 分钟
- 30 天内合并 PR
- 397
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
fluentcms/FluentCMS 的其他 Issue
-
area:host area:operations type:bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:build security type:chore
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:sdk security type:bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:content security type:bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
area:build type:bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
查看 fluentcms/FluentCMS 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 67/100
microsoft/microsoft-ui-reactor#1567 ·
维护者通常 1 天内回复
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
难度 2/5 1-3 小时 新手友好度 76/100
openclaw/openclaw-windows-node#2287 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
kind:ux needs-triage
难度 2/5 1-3 小时 新手友好度 66/100
elsa-workflows/elsa-foundation#4742 ·
维护者通常 1 天内回复
-
priority:P2
难度 2/5 1-3 小时 新手友好度 88/100