Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Rework flaky test detector

已关闭
#24,691 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
重构
描述清晰度
需要澄清
活跃度
活跃
技术栈
github-actions
领域
ci-cd, testing

调研方向

Start by reading the referenced section of .github/workflows/build.yml and the full .github/workflows/flaky-test-detector.yml to understand how each workflow identifies flaky tests and opens issues. Compare their behavior with the backend team's weekly junior report, then define an actionable output that remains viable with merge queues and can support triage.

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

描述

Dev: CI

We have a step in our build workflow that opens issues for tests that fail on develop because we can mostly assume they are flaky:

https://github.com/getsentry/sentry-javascript/blob/b7227bb6c3009218ba7f8c1f1b9074426ecb88e8/.github/workflows/build.yml#L1276

While this is true we keep accumulating these issues (currently >100 open) mostly without ever looking at them. Therefore we should probably rework this workflow a bit to make it more easily actionable. Also if we move to merge queues this workflow will stop working altogether.

We also have this flaky test workflow that I am not yet sure what it does: https://github.com/getsentry/sentry-javascript/blob/develop/.github/workflows/flaky-test-detector.yml

Backend team uses junior to get a list of the most flaky tests each week. Maybe we can do something similar and then make this part of triage or something.

主要语言
TypeScript
星标
8.7k
派生
1.9k
平均合并
1 天 17 小时
30 天内合并 PR
543

环境准备

从这里开始

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

getsentry/sentry-javascript 的其他 Issue

查看 getsentry/sentry-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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