Trim fixed per-scenario overhead

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
php, wordpress

调研方向

Find the code that deletes the scenario RUN_DIR and the step definition for I launch in the background in the PHP test framework. Read #384 to learn the baseline CI timing method, then open a draft PR and run the same CI jobs to record both results. Done means the directory cleanup runs in the background and the process check waits only as needed, with timings posted here.

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

描述

scope:testing status:unconfirmed

A few fixed costs are paid by every scenario, or by every scenario of a kind, without contributing to what is tested:

  1. Removing the scenario's RUN_DIR (about 3,800 files for a WordPress install) blocks the next scenario for about 50 ms. It can happen in the background once the directory is moved out of the way.
  2. Starting a background process (I launch in the background, the PHP built-in web server) always waits a full second before checking that the process is alive, even when it is ready much sooner.

Across all bundled commands, this adds up to roughly 2 to 3 minutes for each CI configuration.

Measuring: take the baseline from #384, then open a draft PR, run the same CI jobs against it and record both results here before we decide.

主要语言
PHP
星标
42
派生
29
平均合并
21 小时 6 分钟
30 天内合并 PR
24

环境准备

从这里开始

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

wp-cli/wp-cli-tests 的其他 Issue

查看 wp-cli/wp-cli-tests 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

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