Skip to content

Conversation

@henrybear327
Copy link
Contributor

@henrybear327 henrybear327 commented Jan 2, 2026

Implement RunWatchLoop in etcd traffic.

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

@serathius
Copy link
Member

/retest

@codecov
Copy link

codecov bot commented Jan 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.57%. Comparing base (a438759) to head (986527e).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files

see 25 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #21071      +/-   ##
==========================================
+ Coverage   68.44%   68.57%   +0.12%     
==========================================
  Files         429      429              
  Lines       35281    35281              
==========================================
+ Hits        24149    24194      +45     
+ Misses       9732     9691      -41     
+ Partials     1400     1396       -4     

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a438759...986527e. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@henrybear327 henrybear327 force-pushed the robustness/watch-refactor-pr2 branch from cc5fa24 to 2e688e4 Compare January 3, 2026 06:12
@henrybear327 henrybear327 marked this pull request as ready for review January 3, 2026 06:24
@henrybear327 henrybear327 force-pushed the robustness/watch-refactor-pr2 branch from 2e688e4 to 23abb59 Compare January 3, 2026 06:30
@henrybear327 henrybear327 changed the title robustness: implement RunWatchLoop and integrate into robustness test [Robustness test] Implement RunWatchLoop and integrate into robustness test Jan 3, 2026
@henrybear327 henrybear327 changed the title [Robustness test] Implement RunWatchLoop and integrate into robustness test [Robustness test] Implement RunWatchLoop and integrate into robustness test (part 2) Jan 3, 2026
@henrybear327 henrybear327 force-pushed the robustness/watch-refactor-pr2 branch 3 times, most recently from 906157f to f4baca0 Compare January 3, 2026 17:09
@henrybear327 henrybear327 force-pushed the robustness/watch-refactor-pr2 branch 2 times, most recently from c8d1332 to 97dc9ba Compare January 4, 2026 07:25
@henrybear327 henrybear327 changed the title [Robustness test] Implement RunWatchLoop and integrate into robustness test (part 2) [Robustness test] Implement RunWatchLoop and integrate into robustness test (part 3) Jan 4, 2026
@henrybear327 henrybear327 requested a review from serathius January 4, 2026 07:30
@serathius
Copy link
Member

Have you verified how this PR changes reproducibility of previous issues found by robustness?

@serathius
Copy link
Member

serathius commented Jan 5, 2026

I think this PR is the best next step as it migrates openWatchPeriodically logic to the new RunWatchLoop.

Left couple of comments, also I'm testing it for reproduction of old watch issues.

@henrybear327 henrybear327 changed the title [Robustness test] Implement RunWatchLoop and integrate into robustness test (part 3) [Robustness test] Implement RunWatchLoop and integrate into robustness test (part 2) Jan 6, 2026
@henrybear327
Copy link
Contributor Author

Have you verified how this PR changes reproducibility of previous issues found by robustness?

This is in progress.

@henrybear327
Copy link
Contributor Author

I think this PR is the best next step as it migrates openWatchPeriodically logic to the new RunWatchLoop.

Left couple of comments, also I'm testing it for reproduction of old watch issues.

Thank you for helping with the testing. I have closed the old part 2 PR and focus on this one instead.

@serathius
Copy link
Member

Please squash commits

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: henrybear327, serathius

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

…or etcd traffic

Signed-off-by: Marek Siarkowicz <[email protected]>
Signed-off-by: Chun-Hung Tseng <[email protected]>
@henrybear327 henrybear327 force-pushed the robustness/watch-refactor-pr2 branch from 388c287 to 986527e Compare January 7, 2026 02:13
@k8s-ci-robot
Copy link

@henrybear327: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-etcd-coverage-report 986527e link true /test pull-etcd-coverage-report

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

MaxNonUniqueRequestConcurrency: 3,
BackgroundWatchConfig: options.BackgroundWatchConfig{
WatchConfig: options.WatchConfig{
Interval: 0,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So you are enabling the mechanism in robustness tests but not in Antithesis? Why?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also interval = 0, means create watch continiously.

return
case <-p.Finish:
return
case <-time.After(p.Interval):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if interval is set to 0 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants