CNTRLPLANE-3427: add script to fetch ci test failures#71
CNTRLPLANE-3427: add script to fetch ci test failures#71ricardomaraschini wants to merge 1 commit into
Conversation
script fetches and analyzes tls-related test failures from openshift's prow ci. it scrapes the latest job results for tls 1.3 adherence and pqc readiness tests, parses junit xml files to extract failed pod names, deduplicates them by stripping kubernetes hash suffixes, and generates a report to tls_failure_report.txt.
openshift-ci-robot
added
the
jira/valid-reference
|
@ricardomaraschini: This pull request references CNTRLPLANE-3427 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 "5.0.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ricardomaraschini The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/jira refresh |
|
@ricardomaraschini: This pull request references CNTRLPLANE-3427 which is a valid jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@ricardomaraschini: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
|
Can you also provide a short README? To see how the script is used and what the output looks like? |
Isn't the comment at the start of the script enough ? |
| jobs = { | ||
| 'tls_adherence': { | ||
| 'name': 'periodic-ci-openshift-tls-scanner-main-periodic-tls13-adherence', | ||
| 'path': '/job-history/gs/test-platform-results/logs/periodic-ci-openshift-tls-scanner-main-periodic-tls13-adherence', |
There was a problem hiding this comment.
Worth making the job name (or at least the branch name) configurable
There was a problem hiding this comment.
My understanding is that this is a job that runs only against a nightly release. What usecase you have in mind for making the branch customizable ?
There was a problem hiding this comment.
Oh, so there's always going to be only the main targeted? In that case please ignore my comment.
Yeah, probably is. After you know the examples are there it is. |
3 participants
script fetches and analyzes tls-related test failures from openshift's prow ci. it scrapes the latest job results for tls 1.3 adherence and pqc readiness tests, parses junit xml files to extract failed pod names, deduplicates them by stripping kubernetes hash suffixes, and generates a report to tls_failure_report.txt.
this script is meant for manual execution as it makes the visualization of the components easier to grasp. if this does not belong here then it is also ok. please let me know.