day-dividers timing test flakes on CI runners

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with day-dividers.test.ts and inspect the "cheap enough to run on every streamed update of a long chat" test and the dividerRows implementation it exercises. Consider whether counting timestamp parses or comparing performance against a same-run baseline would preserve detection of repeated parsing while tolerating runner noise. Done when the check catches a real slowdown without failing from ordinary CI timing variation.

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

描述

type:bug

The day-dividers.test.ts test "cheap enough to run on every streamed update of a long chat" asserts dividerRows stays under 0.5 ms per call on 2000 rows, measured in real time. On a shared CI runner it measured 0.605 ms and failed verify on #768 (run 40546143525), which doesn't touch the renderer.

Acceptance: the check still catches a real slowdown (for example, re-parsing every timestamp on each call) but doesn't fail on runner noise. Options include counting timestamp parses instead of measuring time, or comparing against a baseline taken in the same run.

主要语言
TypeScript
星标
3
派生
0
平均合并
17 小时 33 分钟
30 天内合并 PR
163

环境准备

从这里开始

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

musterhq/muster-code 的其他 Issue

查看 musterhq/muster-code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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