可验证报告、报告导出写「被驳回」:元信息带 end_reason,核对仍按运行取消

为什么:被驳回的运行导出后,可验证报告的运行结果写「已取消」,报告导出的运行状态也写「已取消」,和系统里「被驳回」两种
说法。封存里被驳回和手动停止是同一种结束事件(运行取消),分开它们的原因在那条事件的内容里,而运行取消的内容不随文件
附带(里面有驳回人和备注)——光看封存分不出来。

做了什么:
- 两种导出的元信息都带 end_reason(bundle/build、report_export/build、对应的接口)。
- verifier.js:运行结果按运行记录写「被驳回」,核对的仍是「最后一条结束类事件是运行取消」,旁边写「已核对运行取消,被驳回
  取自运行记录」,原因里写明这一半要去系统里对照;手动停止、老运行照旧「已取消」;文件里写被驳回、事件却是运行结束的照旧
  不通过。runtime.js 的运行状态照 end_reason 写「被驳回」。
- 样本页加一份 rejected(check-bundle 样本数 17 → 18),断言写被驳回、写明取自运行记录、不提重新封存。

测试:test_bundle_rejected 用 node 载入 verifier.js 核运行信息(被驳回、手动停止、老运行、伪造);test_bundle_build 核
元信息和样本页;test_bundle_api 核两种导出接口都带 end_reason。把实现退回去回跑,被驳回、伪造两条和元信息、样本页、
接口的断言都失败(手动停止、老运行两条守的是原样,照旧通过);改完通过。
This commit is contained in:
ThearchyHelios
2026-10-16 12:46:36 +08:00
parent b6cb5816db
commit e96b0180d9
11 changed files with 159 additions and 17 deletions
+18
View File
@@ -353,6 +353,24 @@ async def test_a_failed_run_is_exportable(client, monkeypatch):
assert data_of(resp.text)["meta"]["status"] == "failed"
async def test_a_rejected_run_carries_its_end_reason(client, monkeypatch):
"""被审批人驳回结束的运行(cancelled + end_reason=rejected,05-已知遗留 (a)):可验证报告和报告导出的元信息都带上
end_reason,页面照它写「被驳回」,不写成手动停止的「已取消」。"""
row = await sealed_run(monkeypatch)
async with SessionLocal() as session:
run = await session.get(Run, row.id)
run.status, run.end_reason = "cancelled", "rejected"
await session.commit()
bundle = await client.get(f"/api/runs/{row.id}/bundle.html")
assert bundle.status_code == 200, bundle.text
meta = data_of(bundle.text)["meta"]
assert (meta["status"], meta["end_reason"]) == ("cancelled", "rejected")
report = await client.get(f"/api/runs/{row.id}/report.html")
assert report.status_code == 200, report.text
m = re.search(r'<script type="application/json" id="report-data">(.*?)</script>', report.text, re.S)
assert m and json.loads(m.group(1))["meta"]["end_reason"] == "rejected"
async def test_a_broken_seal_is_refused(client, monkeypatch):
row = await sealed_run(monkeypatch)
async with SessionLocal() as session: