Skip to content

Using processStart time to handle execution delays during stress tests #133354

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Using processStart time to handle execution delays during stress tests #133354

wants to merge 1 commit into from

Conversation

srivastav-abhishek
Copy link
Contributor

What type of PR is this?

/kind bug
/kind flake

What this PR does / why we need it:

Under stress conditions, there is minor execution delay b/w time.Now() and handler initialisation. Used existing processStart time to handle this.

Which issue(s) this PR is related to:

Fixes #132887

Special notes for your reviewer:

Here is the o/p of stress tool with PR change on arm64 arch

% stress ./legacyregistry.test -test.run ^TestProcessStartTimeHeader   


5s: 3089 runs so far, 0 failures, 10 active
10s: 6176 runs so far, 0 failures, 10 active
15s: 9257 runs so far, 0 failures, 10 active
20s: 12390 runs so far, 0 failures, 10 active
25s: 15471 runs so far, 0 failures, 10 active
30s: 18635 runs so far, 0 failures, 10 active
35s: 21644 runs so far, 0 failures, 10 active
40s: 24546 runs so far, 0 failures, 10 active
45s: 27442 runs so far, 0 failures, 10 active
50s: 30404 runs so far, 0 failures, 10 active
55s: 33381 runs so far, 0 failures, 10 active
1m0s: 36396 runs so far, 0 failures, 10 active
1m5s: 39415 runs so far, 0 failures, 10 active
1m10s: 42445 runs so far, 0 failures, 10 active
1m15s: 45432 runs so far, 0 failures, 10 active
1m20s: 48330 runs so far, 0 failures, 10 active
1m25s: 51292 runs so far, 0 failures, 10 active
1m30s: 54340 runs so far, 0 failures, 10 active
1m35s: 57421 runs so far, 0 failures, 10 active
1m40s: 60467 runs so far, 0 failures, 10 active
1m45s: 63412 runs so far, 0 failures, 10 active
1m50s: 66532 runs so far, 0 failures, 10 active
1m55s: 69622 runs so far, 0 failures, 10 active
2m0s: 72739 runs so far, 0 failures, 10 active
2m5s: 75821 runs so far, 0 failures, 10 active
2m10s: 78949 runs so far, 0 failures, 10 active
2m15s: 81750 runs so far, 0 failures, 10 active
2m20s: 84625 runs so far, 0 failures, 9 active
2m25s: 87513 runs so far, 0 failures, 10 active
2m30s: 90372 runs so far, 0 failures, 10 active
2m35s: 93371 runs so far, 0 failures, 10 active
2m40s: 96486 runs so far, 0 failures, 10 active
2m45s: 99498 runs so far, 0 failures, 10 active
2m50s: 102399 runs so far, 0 failures, 10 active
2m55s: 105473 runs so far, 0 failures, 10 active
3m0s: 108476 runs so far, 0 failures, 10 active
3m5s: 111470 runs so far, 0 failures, 10 active
3m10s: 114427 runs so far, 0 failures, 10 active
3m15s: 117560 runs so far, 0 failures, 10 active
3m20s: 120646 runs so far, 0 failures, 10 active
3m25s: 123802 runs so far, 0 failures, 10 active
3m30s: 126950 runs so far, 0 failures, 10 active
3m35s: 130067 runs so far, 0 failures, 10 active
3m40s: 133235 runs so far, 0 failures, 10 active
3m45s: 136386 runs so far, 0 failures, 10 active
3m50s: 139512 runs so far, 0 failures, 10 active
3m55s: 142686 runs so far, 0 failures, 10 active
4m0s: 145880 runs so far, 0 failures, 10 active
4m5s: 148959 runs so far, 0 failures, 10 active
4m10s: 152121 runs so far, 0 failures, 10 active
4m15s: 155310 runs so far, 0 failures, 10 active
4m20s: 158401 runs so far, 0 failures, 10 active
4m25s: 161539 runs so far, 0 failures, 10 active
4m30s: 164735 runs so far, 0 failures, 10 active
4m35s: 167797 runs so far, 0 failures, 10 active
4m40s: 170949 runs so far, 0 failures, 10 active
4m45s: 174070 runs so far, 0 failures, 10 active
4m50s: 177158 runs so far, 0 failures, 10 active
4m55s: 180299 runs so far, 0 failures, 10 active
5m0s: 183475 runs so far, 0 failures, 10 active
5m5s: 186575 runs so far, 0 failures, 10 active
5m10s: 189720 runs so far, 0 failures, 10 active
5m15s: 192899 runs so far, 0 failures, 10 active
5m20s: 196011 runs so far, 0 failures, 10 active
5m25s: 199057 runs so far, 0 failures, 10 active
5m30s: 202242 runs so far, 0 failures, 10 active
5m35s: 205352 runs so far, 0 failures, 10 active
5m40s: 208486 runs so far, 0 failures, 10 active
5m45s: 211653 runs so far, 0 failures, 10 active
5m50s: 214779 runs so far, 0 failures, 10 active
5m55s: 217890 runs so far, 0 failures, 10 active
6m0s: 220972 runs so far, 0 failures, 10 active
6m5s: 224096 runs so far, 0 failures, 10 active
6m10s: 227205 runs so far, 0 failures, 10 active
6m15s: 230381 runs so far, 0 failures, 10 active
6m20s: 233547 runs so far, 0 failures, 10 active
6m25s: 236635 runs so far, 0 failures, 10 active
6m30s: 239819 runs so far, 0 failures, 10 active
6m35s: 242989 runs so far, 0 failures, 10 active
6m40s: 246071 runs so far, 0 failures, 10 active
6m45s: 249175 runs so far, 0 failures, 10 active
6m50s: 252279 runs so far, 0 failures, 10 active
6m55s: 255360 runs so far, 0 failures, 10 active
7m0s: 258492 runs so far, 0 failures, 10 active
7m5s: 261657 runs so far, 0 failures, 10 active
7m10s: 264724 runs so far, 0 failures, 10 active
7m15s: 267669 runs so far, 0 failures, 10 active
7m20s: 270738 runs so far, 0 failures, 10 active
7m25s: 273725 runs so far, 0 failures, 10 active
7m30s: 276689 runs so far, 0 failures, 10 active
7m35s: 279620 runs so far, 0 failures, 10 active
7m40s: 282664 runs so far, 0 failures, 10 active
7m45s: 285795 runs so far, 0 failures, 10 active
7m50s: 288949 runs so far, 0 failures, 10 active
7m55s: 292061 runs so far, 0 failures, 10 active

Does this PR introduce a user-facing change?

None

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. kind/flake Categorizes issue or PR as related to a flaky test. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 1, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: srivastav-abhishek
Once this PR has been reviewed and has the lgtm label, please assign dashpole for approval. For more information see the Code Review Process.

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

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

@srivastav-abhishek
Copy link
Contributor Author

/cc @mkumatag @Rajalakshmi-Girish

@dgrisonnet
Copy link
Member

/assign
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pohly pohly Awaiting requested review from pohly

@richabanker richabanker Awaiting requested review from richabanker

@mkumatag mkumatag Awaiting requested review from mkumatag

@Rajalakshmi-Girish Rajalakshmi-Girish Awaiting requested review from Rajalakshmi-Girish

Assignees

@dgrisonnet dgrisonnet

Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. kind/flake Categorizes issue or PR as related to a flaky test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Flaking Test] UT k8s.io/component-base/metrics: legacyregistry
3 participants
@srivastav-abhishek @k8s-ci-robot @dgrisonnet