OCPBUGS-73893: Fix unit test failure by updating ruby version to 3.3 - #2184
Conversation
|
@ardaguclu: This pull request explicitly references no jira issue. DetailsIn response to this:
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. |
WalkthroughThis change updates the repository context directory path in a test case from version 3.1 to version 3.3, modifying the fixture reference used during app generation testing. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes ✨ Finishing touches
📜 Recent review detailsConfiguration used: Organization UI Review profile: CHILL Plan: Pro Cache: Disabled due to data retention organization setting Knowledge base: Disabled due to 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (1)**⚙️ CodeRabbit configuration file
Files:
🔇 Additional comments (1)
✏️ Tip: You can disable this entire section by setting Comment |
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
pkg/helpers/newapp/newapptest/newapp_test.go (1)
567-609: Consider updating this test case to use3.3as well.If the entire
3.1directory was removed from thesti-rubyrepository, this test passes for the wrong reason — the parent directory doesn't exist rather than the specific subdirectory being missing. To ensure this test validates the intended "missing context dir within a valid version" scenario, update the path to3.3/test/missing-dir.Suggested fix
{ name: "failed app generation using missing context dir", config: &cmd.AppConfig{ ComponentInputs: cmd.ComponentInputs{ SourceRepositories: []string{"https://github.com/openshift/sti-ruby"}, }, GenerationInputs: cmd.GenerationInputs{ - ContextDir: "3.1/test/missing-dir", + ContextDir: "3.3/test/missing-dir", }, ... }, ... errFn: func(err error) bool { - return err.Error() == "supplied context directory '3.1/test/missing-dir' does not exist in 'https://github.com/openshift/sti-ruby'" + return err.Error() == "supplied context directory '3.3/test/missing-dir' does not exist in 'https://github.com/openshift/sti-ruby'" }, },
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting
📒 Files selected for processing (1)
pkg/helpers/newapp/newapptest/newapp_test.go
🧰 Additional context used
📓 Path-based instructions (1)
**
⚙️ CodeRabbit configuration file
-Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity.
Files:
pkg/helpers/newapp/newapptest/newapp_test.go
🔇 Additional comments (1)
pkg/helpers/newapp/newapptest/newapp_test.go (1)
533-533: LGTM!The update from
3.1to3.3correctly addresses the test failure caused by the removal of the ruby:3.1 image tag.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
|
/jira refresh |
|
@ardaguclu: This pull request references Jira Issue OCPBUGS-73893, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
@ardaguclu: This pull request references Jira Issue OCPBUGS-73893, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/cherrypick release-4.21 |
|
@ardaguclu: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ardaguclu, tchap The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified by CI |
|
/retest |
|
@ardaguclu: This PR has been marked as verified by DetailsIn response to this:
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. |
|
/retest |
|
@ardaguclu: all tests passed! 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. |
|
@ardaguclu: Jira Issue Verification Checks: Jira Issue OCPBUGS-73893 Jira Issue OCPBUGS-73893 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
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. |
|
@ardaguclu: new pull request created: #2186 DetailsIn response to this:
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. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-01-19-085729 |
It looks like 3.1 tag of ruby image has been removed and causing our unit test perma-failing. This PR updates the ruby image to 3.3 to fix the test.