Please fix unit test

https://github.com/etcd-io/etcd/actions/runs/3532881659/jobs/5927791293

=== Failed
=== FAIL: transport TestWriteReadTimeoutListener (0.01s)
    timeout_listener_test.go:113: err = EOF, want write i/o timeout error

It maybe a flaky test case.

Let me mark it as draft.

Seems reproductionable. Failed again:

=== Failed
=== FAIL: transport TestWriteReadTimeoutListener (0.01s)
    timeout_listener_test.go:113: err = EOF, want write i/o timeout error

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.53%. Comparing base (a47cdc3) to head (cf285ea).
⚠️ Report is 5727 commits behind head on main.

@@            Coverage Diff             @@
##             main   #14834      +/-   ##
==========================================
- Coverage   75.59%   75.53%   -0.06%     
==========================================
  Files         457      457              
  Lines       37357    37421      +64     
==========================================
+ Hits        28239    28267      +28     
- Misses       7343     7376      +33     
- Partials     1775     1778       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Still working on the failed test case. It is weird. I can't reproduce it in my local. I was thinking that the connection is closed. Let me file issue to track this.

Due to different environment GitHub actions CI frequently flakes on issues that are hard to reproduce locally. I suspect this is due to limited resources, especially CPU. I think you could try to emulate it locally.

Due to different environment GitHub actions CI frequently flakes on issues that are hard to reproduce locally. I suspect this is due to limited resources, especially CPU. I think you could try to emulate it locally.

Yeah. For sure. I am trying to run it limited-resource vm.