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

The unit test host peaks near 8 GB, mostly in Tests.Convenience

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp
领域
testing-qa

调研方向

Start by running dotnet test --filter FullyQualifiedName~Tests.Convenience and watching the test host's resident memory, then compare with DocumentationExamplesRunTest alone. Find which tests in the Tests.Convenience namespace allocate the most, and check whether large inputs or cached results are kept alive across tests. Done means the full suite peaks well under a few GB, or the memory-heavy tests are documented with a reason. The maintainers should confirm which outcome they want before a fix is written.

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

描述

The unit test host peaks near 8 GB on master. Measured on 790feec2 (net10.0, Release), as the test host's resident memory:

Run Peak
whole suite 7,947 MB (killed by a local 8 GB guard in one of two runs)
FullyQualifiedName~Tests.Convenience 5,832 MB in 16 s
DocumentationExamplesRunTest alone 2,505 MB
everything except Tests.Convenience about 1.9 GB
Tests.Calculus 1,763 MB

So most of it comes from Tests.Convenience. On a machine with less memory, or a CI runner with a lower limit, the whole run can be killed mid-way, and vstest still prints Passed! over the tests that finished.

What I'd expect: the suite should stay well under a few GB, or the tests that need that much should say why.

主要语言
C#
星标
831
派生
79
平均合并
2 小时 17 分钟
30 天内合并 PR
443

环境准备

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

从这里开始

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

ASC-Community/AngouriMath 的其他 Issue

查看 ASC-Community/AngouriMath 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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