-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Write test failure summary, and add new command to request failure risk analysis from sippy. #27486
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
Write test failure summary, and add new command to request failure risk analysis from sippy. #27486
Conversation
|
Looks to be working, see the two test-flakes-and-failures files in: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/27486/pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade/1584599588365406208/artifacts/e2e-aws-ovn-single-node-upgrade/single-node-e2e-test/artifacts/junit/ I will remove the extraneous - before the suffix. |
8843bf4 to
cb8d796
Compare
|
Depends on openshift/sippy#657 /hold |
cb8d796 to
296e32d
Compare
This will be used to submit to a new sippy risk analysis API to determine how risky the test failures in this job run are. As with junit xmls, there can be multiple as we often invoke openshift-tests multiple times in one job run. Includes a change to make timestamp suffixes on junit artifacts more consistent.
… and upload. This merges test-flake files, submits them to sippy, and writes the returned risk analysis as an additional artifact. It is intended to be called from the workflow steps that run openshift-tests in the release repo.
296e32d to
19740f0
Compare
pkg/riskanalysis/cmd.go
Outdated
| } | ||
|
|
||
| // TODO: query sippy | ||
| url := "http://localhost:8080/api/jobs/runs/risk_analysis" |
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.
Would we want this to be a config option so we could change down the road without updating the code?
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.
Oops, that should be the real URL.
If sippy moves we'll have to make a commit somewhere, would that be better in release repo to update config, or in origin? Release repo might be a little better as it's probably exempt from code freeze. I could do a CLI flag for this with a default, so it's there if we ever need it.
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.
Having it in the test step (maybe with a default here) makes sense. If it ever changes we'll avoid having to backport the changes
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.
I like the idea of cli flag that can be defaulted and then you can change it in release repo when you call this as a step. Also makes it nice so you can call it locally for testing.
|
|
||
| jr := ProwJobRun{ | ||
| ProwJob: ProwJob{Name: os.Getenv("JOB_NAME")}, | ||
| URL: os.Getenv("JOB_URL"), // just a guess, may not exist |
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.
In this sample podinfo.json from this prow job, there is no JOB_URL. It does have BUILD_ID if you wanted to construct an URL later.
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.
Thanks, I will get this updated in my followup.
|
Looking good to me except the Sippy URL string. |
|
/lgtm |
|
/hold cancel |
|
/hold Sippy URL needs fixing |
|
URL fixed, I will follow up with the CLI arg. |
|
/lgtm |
|
Apologies, I'm going to have to bother folks for another lgtm anyhow, I made the requested modifications in this PR. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DennisPeriquet, dgoodwin, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold cancel |
|
/override ci/prow/e2e-gcp-ovn-upgrade Failing on disruption. |
|
@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-gcp-ovn-upgrade DetailsIn 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 kubernetes/test-infra repository. |
|
@dgoodwin: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
/cherry-pick release-4.12 |
|
@dgoodwin: new pull request created: #27520 DetailsIn 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 kubernetes/test-infra repository. |
This change begins writing out a brief test failure summary artifact in a format that is logical and also deserializable by sippy.
It also adds a new sub-command that can be used to merge several of these files, submit them to sippy, and write the resulting risk analysis to the artifacts directory.
Requires openshift/sippy#657
TRT-602