[Integration Test Failures] Tracking bug
- 主要言語
- Dart
- スター
- 1.7k
- フォーク
- 404
- 平均マージ
- 6日 17時間
- マージ済み PR（30日）
- 18
説明
Some of our integration tests have suddenly begun failing. This is a tracking bug for the investigation and fixes.
Possibly related to Chrome / ChromeDriver update, since no changes have been made in DevTools.
### Successful run
- https://github.com/flutter/devtools/actions/runs/21402249586/job/61616639862
- [logs_55563736520.zip](https://github.com/user-attachments/files/24974445/logs_55563736520.zip)
### Unsuccessful run
- https://github.com/flutter/devtools/actions/runs/21527631142/job/62035399292?pr=9638
- [logs_55943496892.zip](https://github.com/user-attachments/files/24974456/logs_55943496892.zip)
コントリビューションガイド
調査の方向性
Start by comparing the successful and unsuccessful GitHub Actions runs and their attached log archives. Investigate the reported Chrome/ChromeDriver update relationship and identify which integration tests fail. Done means the failures are fixed and a subsequent integration-test run succeeds.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- dart, github-actions
- 領域
- testing, tooling
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100