I'm building a flaky-test finder with Spring Boot, Go and SQS (v0.1.0)
说明与用途
FlakeSince 收集 CI 测试结果,存储到 PostgreSQL,并确保每次运行仅记录一次,从而实现对不稳定测试的检测和历史追踪。
问题
Flaky tests cause CI builds to fail intermittently, wasting time re‑running and investigating failures.
结果
FlakeSince reliably ingests CI test results, preserves full history, and ensures each run is stored exactly once, enabling future flaky‑test detection and analysis.
工作流
- 1. GitHub Action uploads JUnit XML files to FlakeSince action.
- 2. Go ingest service validates API key, parses XML, and enqueues a message per CI run to SQS.
- 3. SQS (or ElasticMQ locally) holds the message until processed.
- 4. Spring Boot API reads the queue, checks for duplicates, saves the run to PostgreSQL, and deletes the message upon success.
- 5. If processing fails three times, the message moves to a dead‑letter queue.
证据
FlakeSince keeps the pass/fail history of every normal CI run, so it can also estimate since which commit a test became flaky, without re‑running anything.
A small Go ingest service checks the API key, parses the XML and puts one message per CI run on a queue.
If saving fails 3 times, the message goes to a dead‑letter queue instead of being lost.
- 记录日期: 2026-10-26T08:11:18.702Z