Per-run / per-case test log isolation for PresentMonAPI2Tests

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by locating PresentMonAPI2Tests, TEST_MODULE_INITIALIZE, and the shared TestArtifacts helper, then trace how PMON_TEST_RUN_ID and PMON_TEST_RUN_ID_FILE control run rotation. Check the CTest fixture and agent script paths mentioned in the issue. Done means each case keeps its own logs and output, runs rotate with one .prev retained, and wipe failures are recorded while execution continues.

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

描述

Problem

PresentMonAPI2Tests write shared suite folders under TestLogs\<Suite> and TestOutput\<Suite>. TEST_MODULE_INITIALIZE used to wipe a hand-maintained list of those folders, which is a poor fit for current runners:

  • CTest loads the DLL once per method, so a wipe either destroys earlier cases in the same ctest invocation or never clears unlisted suites (e.g. CaptureCliWait, UiLaunch).
  • Shared suite folders let log assertions (e.g. ClientLogContains_ in CaptureCliWaitTests) match stale files from prior cases or runs.
  • We need post-mortem data after failures; cavalier deletion of the current run's artifacts is not acceptable.
Proposed solution

Keep every case's logs for the duration of a run; rotate only between runs; keep one previous run as .prev.

  • Shared helper (TestArtifacts) decides rotate vs join from PMON_TEST_RUN_ID / PMON_TEST_RUN_ID_FILE (CTest fixture + agent script) or standalone (IDE / manual vstest).
  • Per-case folders: TestLogs\<Suite>\<NNNN>-<label>\ with case.txt, child process logs, and output\.
  • Preserve AgentDiagnostics for the agent script; reset MachineExpectations with the output root each run; wipe failures warn and continue (rotation-warnings.txt).
主要语言
C++
星标
2.6k
派生
201
平均合并
2 天 21 小时
30 天内合并 PR
16

环境准备

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

从这里开始

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

GameTechDev/PresentMon 的其他 Issue

查看 GameTechDev/PresentMon 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

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