Flaky: NetworkFailureRecorderLiveTest.chrome_cdp_recordsFailedRequestsOnly

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with NetworkFailureRecorderLiveTest.chrome_cdp_recordsFailedRequestsOnly and the recorder it drives, which assembles method and URL from CDP events; the failure is that requestWillBeSent can arrive after the response, so the fallback defaults get recorded. Run the test in a loop to reproduce the roughly 1-in-5 failure. Done when the method and URL survive out-of-order events, or the test waits for both events, and it passes 20 out of 20 runs locally.

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

描述

bug

Fails about 1 run in 5 locally on unmodified master (2a07bba), with Chrome reporting CDP 157 while Selenium tops out at 156.

When it fails, the /fail request (a POST in the page) is recorded as GET ... 500, and a GET (unknown) 0 net::ERR_CONNECTION_REFUSED entry has no URL, so the method and URL assertions miss:

[GET http://127.0.0.1:<port>/fail 500 null, GET (unknown) 0 net::ERR_CONNECTION_REFUSED, GET http://127.0.0.1:<port>/missing 404 null]

This looks like CDP events for the same request arriving out of order (the response before requestWillBeSent), so the recorder falls back to defaults. Found while verifying #254, which doesn't touch tracing.

Done when: the recorder keeps the method and URL when events arrive out of order, or the test waits for the events properly, and the test passes 20/20 locally.

主要语言
Java
星标
12
派生
6
平均合并
10 小时
30 天内合并 PR
76

环境准备

从这里开始

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

seleniumboot/selenium-boot 的其他 Issue

查看 seleniumboot/selenium-boot 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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