Skip to content

Conversation

kstrenkova
Copy link
Contributor

Currently when running Tempest tests multiple times, it always starts without any information. This patch adds a possibility to reuse timing data from the first Tempest run, so it saves time the next run.

Copy link
Contributor

openshift-ci bot commented Aug 6, 2025

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

Copy link
Contributor

openshift-ci bot commented Aug 6, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kstrenkova
Once this PR has been reviewed and has the lgtm label, please assign stuggi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

Currently when running Tempest tests multiple times, it always
starts without any information. This patch adds a possibility
to reuse timing data from the first Tempest run, so it saves time
the next run.
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@sdatko
Copy link
Contributor

sdatko commented Aug 29, 2025

Closing in favor of #316 (preserving the data across multiple job instances, not only within the same environment)

@sdatko sdatko closed this Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants