-
Notifications
You must be signed in to change notification settings - Fork 4.8k
TRT-1678: write the install upgrade and e2e duration metrics #30534
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.
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
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
Scheduling required tests: Scheduling tests matching the |
|
@jianlinliu: This pull request references TRT-1678 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set. In response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Scheduling required tests: Scheduling tests matching the |
|
/cc |
pkg/test/ginkgo/cmd_runsuite.go
Outdated
| logrus.Infof("Retry strategy %s decided not to retry %d failing tests", o.RetryStrategy.Name(), fail) | ||
| } | ||
|
|
||
| end := time.Now() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is interesting, I wonder if there is any value in tracking the time for e2e before the retries as well as the total e2e time with the retries...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This morning, I misunderstood the comment a bit. Now I introduced a new set of variables for retries to track the overall e2e duration with retries together with the e2e duration before retries. Now it should make everyone be happy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the total time duration of a run suite, you can probably just move end to incorporate retries in the total duration.
If you wanted to create a new metric to count retries in their own block that might be interesting to see how much time we spend on them
pkg/dataloader/types.go
Outdated
| return nil | ||
| } | ||
|
|
||
| // WriteDurations writes multiple duration metrics to a file in the autodol format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo autodol -> autodl
I feel like this function would fit better under e2eanalysis either as a separate util or in e2eanalysis.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. Moved it to e2eanalysis.go
|
Scheduling required tests: Scheduling tests matching the |
|
Scheduling required tests: Scheduling tests matching the |
|
Scheduling required tests: Scheduling tests matching the |
|
Job Failure Risk Analysis for sha: eae382f
|
|
/test e2e-vsphere-ovn |
|
/test e2e-gcp-ovn-upgrade |
|
Per the test result, install duration ( |
|
/verified by @jianlinliu |
|
@jianlinliu: This PR has been marked as verified by In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-gcp-ovn-upgrade enabled the cloud function to pull in these artifacts for validation |
pkg/e2eanalysis/e2e_analysis.go
Outdated
| }, | ||
| Rows: rows, | ||
| } | ||
| fileName := filepath.Join(artifactDir, fmt.Sprintf("duration-metric-%s%s-%s", name, timeSuffix, dataloader.AutoDataLoaderSuffix)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duration-metrics here as well
pkg/e2eanalysis/e2e_analysis.go
Outdated
| } | ||
|
|
||
| dataFile := dataloader.DataFile{ | ||
| TableName: "duration-metric", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
apologies for missing this before, could you make this plural duration-metrics
pkg/test/ginkgo/cmd_runsuite.go
Outdated
| logrus.Infof("Retry strategy %s decided not to retry %d failing tests", o.RetryStrategy.Name(), fail) | ||
| } | ||
|
|
||
| end_with_retries := time.Now() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
endWithRetries
Please follow https://go.dev/doc/effective_go#mixed-caps
|
Scheduling required tests: Scheduling tests matching the |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jianlinliu, neisw The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified by @jianlinliu |
|
@jianlinliu: This PR has been marked as verified by In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/label acknowledge-critical-fixes-only this is data we want to start collecting for 4.21 |
|
@jianlinliu: all tests passed! Full PR test history. Your PR dashboard. 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. |
No description provided.