search

openshift / cluster-node-tuning-operator

Manage node-level tuning by orchestrating the tuned daemon.
Apache License 2.0
102 stars 105 forks source link

DNM WIP test patch on BM job #977

Closed sshnaidm closed 1 month ago

openshift-ci[bot] commented 8 months ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sshnaidm Once this PR has been reviewed and has the lgtm label, please assign ffromani for approval. For more information see the Kubernetes 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: - **[OWNERS](https://github.com/openshift/cluster-node-tuning-operator/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
sshnaidm commented 8 months ago

/hold

sshnaidm commented 8 months ago

/test e2e-telco5g-cnftests

sshnaidm commented 6 months ago

/test e2e-telco5g-cnftests

sshnaidm commented 6 months ago

/test e2e-telco5g-cnftests

sshnaidm commented 6 months ago

/test e2e-telco5g-cnftests-sno

openshift-ci[bot] commented 6 months ago

@sshnaidm: The specified target(s) for /test were not found. The following commands are available to trigger required jobs:

The following commands are available to trigger optional jobs:

Use /test all to run the following jobs that were automatically triggered:

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/977#issuecomment-2127598907): >/test e2e-telco5g-cnftests-sno Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
openshift-ci[bot] commented 6 months ago

@sshnaidm: 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-gcp-pao-updating-profile ef8682343667750af5bc217e58ebe87c1bb34678 link true /test e2e-gcp-pao-updating-profile
ci/prow/e2e-gcp-pao ef8682343667750af5bc217e58ebe87c1bb34678 link true /test e2e-gcp-pao
ci/prow/e2e-hypershift ef8682343667750af5bc217e58ebe87c1bb34678 link true /test e2e-hypershift
ci/prow/e2e-aws-ovn-techpreview ef8682343667750af5bc217e58ebe87c1bb34678 link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn ef8682343667750af5bc217e58ebe87c1bb34678 link true /test e2e-aws-ovn
ci/prow/e2e-aws-operator ef8682343667750af5bc217e58ebe87c1bb34678 link true /test e2e-aws-operator
ci/prow/e2e-gcp-pao-workloadhints ef8682343667750af5bc217e58ebe87c1bb34678 link true /test e2e-gcp-pao-workloadhints
ci/prow/e2e-upgrade ef8682343667750af5bc217e58ebe87c1bb34678 link true /test e2e-upgrade
ci/prow/e2e-telco5g-cnftests ef8682343667750af5bc217e58ebe87c1bb34678 link false /test e2e-telco5g-cnftests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-bot commented 3 months ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 2 months ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 1 month ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci[bot] commented 1 month ago

@openshift-bot: Closed this PR.

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/977#issuecomment-2427948158): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.