openshift
TRT-2423: feat(tests): add BigQuery-based test duration tracking
Similar to #30445, but includes duration information for all tests from BigQuery. Not sure if the duration JSON generator should live here or elsewhere, probably elsewhere given the dependency size (ci-tools?)
Add test duration query functionality from BigQuery and implement duration-aware test sorting to optimize test suite execution order. Includes new "generate durations" command and required dependencies.
Pipeline controller notification
This repository is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.
For optional jobs, comment /test ? to see a list of all defined jobs. Review these jobs and use /test <job> to manually trigger optional jobs most likely to be impacted by the proposed changes.
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: stbenjam
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [stbenjam]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@stbenjam: This pull request references TRT-2423 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 task to target the "4.21.0" version, but no target version was set.
In response to this:
Add test duration query functionality from BigQuery and implement duration-aware test sorting to optimize test suite execution order. Includes new "generate durations" command and required dependencies.
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.
@stbenjam: This pull request references TRT-2423 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 task to target the "4.21.0" version, but no target version was set.
In response to this:
Similar to 30445, but includes duration information for all tests from BigQuery. Not sure if the duration JSON generator should live here or elsewhere, probably elsewhere given the dependency size (ci-tools?)
Add test duration query functionality from BigQuery and implement duration-aware test sorting to optimize test suite execution order. Includes new "generate durations" command and required dependencies.
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.
@stbenjam: This pull request references TRT-2423 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 task to target the "4.21.0" version, but no target version was set.
In response to this:
Similar to #30445, but includes duration information for all tests from BigQuery. Not sure if the duration JSON generator should live here or elsewhere, probably elsewhere given the dependency size (ci-tools?)
Add test duration query functionality from BigQuery and implement duration-aware test sorting to optimize test suite execution order. Includes new "generate durations" command and required dependencies.
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.
Interesting that 30493 - aws-ovn-fips ran for 2h59m9s but 30445 - aws-ovn-fips was 2h17m31s that one is out of date so not a fair comparison I guess.
@stbenjam: 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-metal-ipi-ovn-ipv6 | df48c54d10a546cb78674195ff394ae70d90ffcb | link | true | /test e2e-metal-ipi-ovn-ipv6 |
| ci/prow/e2e-aws-ovn-fips | 5a75e73c9878a15fdce375450e7822f61c0667ef | link | true | /test e2e-aws-ovn-fips |
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.