Skip to content

WIP: test CI job with CNF#77795

Open
sshnaidm wants to merge 1 commit intoopenshift:mainfrom
sshnaidm:testci1
Open

WIP: test CI job with CNF#77795
sshnaidm wants to merge 1 commit intoopenshift:mainfrom
sshnaidm:testci1

Conversation

@sshnaidm
Copy link
Copy Markdown
Contributor

@sshnaidm sshnaidm commented Apr 14, 2026

Summary by CodeRabbit

  • Chores
    • Minor updates to test infrastructure files.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 14, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sshnaidm

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

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 14, 2026

Walkthrough

A single trailing comment line (# test) was added at the end of a shell script file after the exit statement. No logic, control flow, or error handling was modified.

Changes

Cohort / File(s) Summary
Shell Script Comment
ci-operator/step-registry/telco5g/cnf/tests/telco5g-cnf-tests-commands.sh
Single comment line (# test) appended after the exit statement with no functional changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 9 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'WIP: test CI job with CNF' is vague and generic, using non-descriptive terms that don't convey the specific change made (adding a trailing comment to a test script). Replace with a more specific title that describes the actual change, such as 'Add trailing comment to telco5g CNF test script' or clarify the purpose of the CI job modification.
✅ Passed checks (9 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names ✅ Passed PR modifies only a shell script file, not Ginkgo test files. No dynamic information in test names is present.
Test Structure And Quality ✅ Passed The custom check targets Ginkgo test code quality, but the modified bash CI/CD orchestration script contains no Ginkgo test blocks or assertions.
Microshift Test Compatibility ✅ Passed PR adds only a trailing comment to a bash script; no new Ginkgo e2e tests are introduced.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR modifies only a shell script (telco5g-cnf-tests-commands.sh) by adding a trailing comment, not introducing any Ginkgo e2e tests.
Topology-Aware Scheduling Compatibility ✅ Passed This PR modifies only a CI test shell script by adding a trailing comment, introducing no scheduling directives or deployment manifest changes.
Ote Binary Stdout Contract ✅ Passed PR modifies a bash shell script by adding an unreachable comment after exit statement. Not an OTE binary or Go test binary.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only adds a trailing comment to a shell script, not new Ginkgo e2e tests as required by this check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from stbenjam and xueqzhan April 14, 2026 17:06
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
ci-operator/step-registry/telco5g/cnf/tests/telco5g-cnf-tests-commands.sh (1)

834-834: Remove or clarify the trailing WIP comment.

Line 834 (# test) looks like a temporary debug marker. Since it sits after exit ${status}, it adds noise without value; please remove it or replace it with a meaningful comment if intentional.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@ci-operator/step-registry/telco5g/cnf/tests/telco5g-cnf-tests-commands.sh` at
line 834, Remove the stray debug comment "# test" that appears after the
script's final "exit ${status}"—either delete that line entirely or replace it
with a meaningful comment describing why anything after the exit exists (if
intentional); locate the trailing comment following the "exit ${status}" in
telco5g-cnf-tests-commands.sh and remove or clarify it to avoid noisy leftover
WIP markers.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@ci-operator/step-registry/telco5g/cnf/tests/telco5g-cnf-tests-commands.sh`:
- Line 834: Remove the stray debug comment "# test" that appears after the
script's final "exit ${status}"—either delete that line entirely or replace it
with a meaningful comment describing why anything after the exit exists (if
intentional); locate the trailing comment following the "exit ${status}" in
telco5g-cnf-tests-commands.sh and remove or clarify it to avoid noisy leftover
WIP markers.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ecf36636-b0c5-4f61-ae9c-296a0472fe60

📥 Commits

Reviewing files that changed from the base of the PR and between b780ca6 and 9544436.

📒 Files selected for processing (1)
  • ci-operator/step-registry/telco5g/cnf/tests/telco5g-cnf-tests-commands.sh

@sshnaidm
Copy link
Copy Markdown
Contributor Author

/uncc @stbenjam
/uncc @xueqzhan

@openshift-ci openshift-ci bot removed request for stbenjam and xueqzhan April 14, 2026 17:07
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@sshnaidm: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-cluster-node-tuning-operator-main-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-5.0-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.23-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.22-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.21-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.20-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.19-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.18-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.17-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.16-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-cluster-node-tuning-operator-release-4.15-e2e-telco5g-cnftests openshift/cluster-node-tuning-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-main-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-5.0-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-4.23-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-4.22-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-4.21-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-4.20-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-4.19-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-4.18-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-4.17-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-sriov-network-operator-release-4.16-e2e-telco5g-sriov-sno openshift/sriov-network-operator presubmit Registry content changed
pull-ci-openshift-kni-cnf-features-deploy-master-e2e-telco5g-cnftests openshift-kni/cnf-features-deploy presubmit Registry content changed
pull-ci-openshift-kni-cnf-features-deploy-release-4.20-e2e-telco5g-cnftests openshift-kni/cnf-features-deploy presubmit Registry content changed
pull-ci-openshift-kni-cnf-features-deploy-release-4.19-e2e-telco5g-cnftests openshift-kni/cnf-features-deploy presubmit Registry content changed
pull-ci-openshift-kni-cnf-features-deploy-release-4.18-e2e-telco5g-cnftests openshift-kni/cnf-features-deploy presubmit Registry content changed

A total of 51 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@sshnaidm
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-cnftests periodic-ci-openshift-release-main-nightly-4.23-e2e-telco5g-cnftests periodic-ci-openshift-release-main-nightly-4.22-e2e-telco5g-cnftests periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-mno-ztp-cnftests periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-sno-ztp-cnftests periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-sno-cnftests

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@sshnaidm: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@sshnaidm: job(s): either don't exist or were not found to be affected, and cannot be rehearsed

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 14, 2026

@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/rehearse/periodic-ci-openshift-release-main-nightly-4.22-e2e-telco5g-cnftests 9544436 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-telco5g-cnftests
ci/rehearse/periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-sno-ztp-cnftests 9544436 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-sno-ztp-cnftests
ci/rehearse/periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-mno-ztp-cnftests 9544436 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-mno-ztp-cnftests
ci/rehearse/periodic-ci-openshift-release-main-nightly-4.23-e2e-telco5g-cnftests 9544436 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-4.23-e2e-telco5g-cnftests
ci/rehearse/periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-cnftests 9544436 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-telco5g-cnftests

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant