WIP/DO NOT MERGE: Testing setup jobs of cri-o#80832
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ngopalak-redhat The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
WalkthroughThe SSH heredoc in ChangesCRI-O SSH Setup Heredoc Refactor
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error, 1 inconclusive)
✅ Passed checks (13 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/hold |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@ci-operator/step-registry/cri-o/setup/test/cri-o-setup-test-commands.sh`:
- Around line 16-17: The directory path referenced in the cd command on line 17
does not match the extracted archive from line 16. When downloading from the
GitHub archive URL with the branch name fix-libpathrs-0.2.5, the extracted
directory will be named cri-o-fix-libpathrs-0.2.5, not cri-o-pin-runc-version.
Update the cd command to use the correct extracted directory name that
corresponds to the branch name in the curl download URL to ensure the path
exists before attempting to change into it.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: 4280faa0-e752-47b9-848a-9ca9f18f8281
📒 Files selected for processing (1)
ci-operator/step-registry/cri-o/setup/test/cri-o-setup-test-commands.sh
|
/pj-rehearse |
|
@ngopalak-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse periodic-ci-cri-o-cri-o-main-periodics-setup-periodic |
|
@ngopalak-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@ngopalak-redhat: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/pj-rehearse periodic-ci-cri-o-cri-o-main-periodics-setup-periodic |
|
@ngopalak-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Summary by CodeRabbit
This PR introduces a new test step script for the cri-o setup workflow in the OpenShift CI infrastructure. The change adds
cri-o-setup-test-commands.sh, which is invoked as part of thecri-o-setupworkflow to test the setup jobs for cri-o.The script implements a GCP-based test workflow that:
ngopalak-redhat/cri-oon thefix-libpathrs-0.2.5branch) and extracts it to/tmpsetup-main.yml) from the extracted source'scontrib/test/cidirectory in local connection mode to run the setup testsThis new test step integrates into the existing cri-o-setup workflow that includes VCP provisioning, build host setup, and cleanup steps. The script is part of the OpenShift CI infrastructure's step registry, which is used to modularize and reuse CI job components across different repositories and test scenarios.