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
523

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

getsentry/sentry-javascript 的其他 Issue

查看 getsentry/sentry-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。