Files
streamline/control-server/test/mr_failure_reason.test.ts
2026-11-16 17:26:44 -08:00

63 lines
3.4 KiB
TypeScript
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
// MUST be first — pins env before anything that reads it at module load.
import "./setup_env";
import { test, expect, describe } from "bun:test";
import { awaitingOwnerDevTaskReason, isMrClickPendingReason, isMrSubmissionFailureReason } from "../src/bits";
import { repoByKey } from "@bbbug/shared/repos";
/**
* Which `failureReason` strings count as "stale MR-submission noise" once the
* item has an MR. Getting this wrong in either direction is bad: too loose and a
* real run failure (Fix-Critic verdict, agent error) gets silently erased; too
* tight and a working MR keeps a red banner next to it forever.
*/
describe("isMrSubmissionFailureReason", () => {
test("matches what the MR pipeline writes", () => {
expect(isMrSubmissionFailureReason('MR 提交失败(as jingyuan.yi):create_mr: HTTP 200: {"code":400}')).toBe(true);
expect(isMrSubmissionFailureReason("MR 提交异常:fetch failed")).toBe(true);
});
test("null / empty is not a failure", () => {
expect(isMrSubmissionFailureReason(null)).toBe(false);
expect(isMrSubmissionFailureReason("")).toBe(false);
});
test("leaves a run's own failure alone", () => {
expect(isMrSubmissionFailureReason("Fix-Critic 判定 SCENARIO_BANDAID,已自动打回重修")).toBe(false);
expect(isMrSubmissionFailureReason("Agent exited with STATUS: IMPLEMENTATION_FAILED")).toBe(false);
// Only the leading position counts — an MR complaint quoted inside a longer
// run failure is still a run failure.
expect(isMrSubmissionFailureReason("编译失败,顺带 MR 提交失败")).toBe(false);
});
});
/**
* 「等人点一下建 MR」借用了 failureReason 这条管道,但它不是失败。飞书卡片按这个
* 判定把标题从「失败原因」换成「待你操作」—— 判错的代价是让一个待办读成一次事故。
*/
describe("isMrClickPendingReason", () => {
const OLD_CLICK = "MR 提交失败(as johnlee):preflight: 分支 feature/x 推在 tt_im_monorepo,"
+ "这个仓的 MR 不自动建,需要在面板上点「创建 MR」发起。也可以直接自己建:https://code.byted.org/…";
const DEV_TASK_CLICK = "MR 提交失败(as johnlee):preflight: 分支 feature/x 推在 tt_im_monorepo,"
+ "这个仓的开发任务不自动建,需要在面板上点「创建开发任务」发起。";
test("认得出新开发任务文案,也兼容数据库里的旧 MR 文案", () => {
expect(isMrClickPendingReason(DEV_TASK_CLICK)).toBe(true);
expect(isMrClickPendingReason(OLD_CLICK)).toBe(true);
const awaiting = "MR 提交失败(as wangshuo.frontend):"
+ awaitingOwnerDevTaskReason(repoByKey("tt-im-monorepo")!, "feature/x", "wangshuo.frontend");
expect(isMrClickPendingReason(awaiting)).toBe(true);
});
test("真失败不会被当成待办", () => {
expect(isMrClickPendingReason('MR 提交失败(as srj.5):create_mr: HTTP 200: {"code":400}')).toBe(false);
expect(isMrClickPendingReason("Fix-Critic 判定证据不足")).toBe(false);
expect(isMrClickPendingReason(null)).toBe(false);
});
test("正文里提到「创建 MR」但不是 MR 流水线写的 —— 不接管", () => {
expect(isMrClickPendingReason("复核意见:需要在面板上点「创建 MR」发起吗?")).toBe(false);
expect(isMrClickPendingReason("复核意见:需要在面板上点「创建开发任务」发起吗?")).toBe(false);
});
});