TRT-2172: Generate autodl artifact to study e2e tests correlated with high CPU

[dgoodwin]

Look for e2e test intervals that overlap with high CPU alerts, be they
pending or firing. Output a datafile that will be automatically ingested
into bigquery where we can then study what tests are failing due to high
CPU, and perhaps what tests are causing it.

[openshift-ci-robot]

@dgoodwin: This pull request references TRT-2172 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.20.0" version, but no target version was set.

In response to this:

Look for e2e test intervals that overlap with high CPU alerts, be they
pending or firing. Output a datafile that will be automatically ingested
into bigquery where we can then study what tests are failing due to high
CPU, and perhaps what tests are causing it.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin

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:

• OWNERS [dgoodwin]

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

[openshift-ci]

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

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-etcd-scaling	bd1dd2c	link	false	/test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-single-node	bd1dd2c	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-gcp-fips-serial-2of2	bd1dd2c	link	false	/test e2e-gcp-fips-serial-2of2
ci/prow/e2e-aws-ovn-microshift	bd1dd2c	link	true	/test e2e-aws-ovn-microshift
ci/prow/e2e-aws-ovn-single-node-upgrade	bd1dd2c	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-disruptive	bd1dd2c	link	false	/test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-serial-publicnet-1of2	bd1dd2c	link	false	/test e2e-aws-ovn-serial-publicnet-1of2
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6	bd1dd2c	link	false	/test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-azure-ovn-etcd-scaling	bd1dd2c	link	false	/test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	bd1dd2c	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-disruptive	bd1dd2c	link	false	/test e2e-gcp-disruptive
ci/prow/e2e-gcp-ovn-etcd-scaling	bd1dd2c	link	false	/test e2e-gcp-ovn-etcd-scaling
ci/prow/okd-e2e-gcp	bd1dd2c	link	false	/test okd-e2e-gcp
ci/prow/e2e-vsphere-ovn-etcd-scaling	bd1dd2c	link	false	/test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-aws	bd1dd2c	link	false	/test e2e-aws
ci/prow/e2e-openstack-serial	bd1dd2c	link	false	/test e2e-openstack-serial
ci/prow/e2e-gcp-fips-serial-1of2	bd1dd2c	link	false	/test e2e-gcp-fips-serial-1of2
ci/prow/e2e-azure-ovn-upgrade	bd1dd2c	link	false	/test e2e-azure-ovn-upgrade

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.

[openshift-trt]

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: bd1dd2c

• "[Jira:"Test Framework"] monitor test high-cpu-test-analyzer cleanup" [Total: 48, Pass: 48, Fail: 0, Flake: 0]
• "[Jira:"Test Framework"] monitor test high-cpu-test-analyzer collection" [Total: 48, Pass: 48, Fail: 0, Flake: 0]
• "[Jira:"Test Framework"] monitor test high-cpu-test-analyzer interval construction" [Total: 48, Pass: 48, Fail: 0, Flake: 0]
• "[Jira:"Test Framework"] monitor test high-cpu-test-analyzer preparation" [Total: 48, Pass: 48, Fail: 0, Flake: 0]
• "[Jira:"Test Framework"] monitor test high-cpu-test-analyzer setup" [Total: 48, Pass: 48, Fail: 0, Flake: 0]
• "[Jira:"Test Framework"] monitor test high-cpu-test-analyzer test evaluation" [Total: 48, Pass: 48, Fail: 0, Flake: 0]
• "[Jira:"Test Framework"] monitor test high-cpu-test-analyzer writing to storage" [Total: 48, Pass: 48, Fail: 0, Flake: 0]