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

humility test suite could be less needlessly cruel

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

还没有人认领这个 Issue。

评估

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

调研方向

首先运行 Humility 测试套件,并找到构成按 core 划分的命令矩阵的测试框架。检查 humility counters 等命令在不同 core 上的行为。完成的标准是:可以将命令限制在相关的 core 上,同时保持现有的覆盖率,并使测试套件避免重复运行。

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

描述

Running the Humility test suite is one of the most unkind things I've done to my poor laptop: it takes about five minutes to run, and pins every CPU core at 100% for the entire duration:
image

It seems like this is because the complexity of the test suite is multiplicative: it's the number of cores times the number of commands we run. This means that adding a new command increases the total size of the test suite by len(cores), and adding a new core increases the total size of the test suite by len(commands).

There's probably a way to make this a bit less of a brutal dev machine torture test: in at least some cases, such as counters, a command is only "interesting" to run on newer cores that contain the structures the command interprets. Running humility counters on any core except for the one I added specifically to test the counters will just result in humility error: no counters found. So, we probably don't need to run the several different counters commands in the test suite against every core we currently test with. If we added a notion of "only run this command against these cores" to the test framework, we could make it a little less painful to run.

主要语言
Rust
星标
587
派生
64
平均合并
2 天 1 小时
30 天内合并 PR
7

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

oxidecomputer/humility 的其他 Issue

查看 oxidecomputer/humility 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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