Emacs Lisp: `eask run command <name>` (a user-defined Eask command running ert) is not a test run

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
emacs-lisp, python
领域
testing-qa

调研方向

The false FAIL comes from the Emacs Lisp test-detection check in the Python validator; find the rule that requires a CI command matching eask test ert and extend it to recognise eask run command <name> by reading the named eask-defcommand in the Eask file. Reproduce with the repro case in the issue (an Eask file defining a command that runs ert, with CI calling eask run command test) and confirm it no longer reports FAIL, accepting PASS or unknown.

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

描述

emacs-evil/evil's make test runs eask run command test, an Eask command that loads evil-tests.el (235 ert-deftests) and runs them → FAIL "no CI configuration runs eask test ert …". The Eask file's commands are readable.

Evidence from the corpus audit

emacs-evil/evil / tests-run
  • kind: FALSE_NEGATIVE
  • actual: FAIL: Emacs Lisp: tests found in 1 file(s), but no CI configuration runs eask test ert test/*.el (...)
  • expected: PASS (or ERROR): CI's make test runs eask run command test, a user-defined Eask command that loads evil-tests.el (235 ert-deftests) and runs them.
  • evidence: .github/workflows/test.yml:53: make test; Makefile:37-38: test: / $(EASK) run command test; Eask:25-28: (eask-defcommand test ... (require 'evil-tests) / (evil-tests-initialize nil nil)).
  • repro: Eask with (eask-defcommand test (require 'x-tests) (ert-run-tests-batch-and-exit)) and CI eask run command test.
  • confidence: medium (the command body is Elisp; "unknown" would be acceptable, silent FAIL is not)

Found by the regression-corpus audit (235 real repositories, one or more per ecosystem profile; corpus and expected results in corpus/). Evidence is quoted from the audited checkouts at the commits pinned in corpus/projects.toml; <checkouts>/<owner>__<repo> is such a checkout.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

主要语言
Python
星标
4
派生
1
平均合并
10 小时 41 分钟
30 天内合并 PR
79

环境准备

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

从这里开始

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

cpp-best-practices/project_validator 的其他 Issue

查看 cpp-best-practices/project_validator 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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