Skip to content

Adding buffer to BeforeSuite tests#358

Merged
openshift-merge-bot[bot] merged 1 commit intoopendatahub-io:mainfrom
mholder6:updating-tests
Jun 25, 2025
Merged

Adding buffer to BeforeSuite tests#358
openshift-merge-bot[bot] merged 1 commit intoopendatahub-io:mainfrom
mholder6:updating-tests

Conversation

@mholder6
Copy link

@mholder6 mholder6 commented Jun 25, 2025

Added a buffer to the BeforeSuite tests to give the deployments more time to become ready in the CI tests.

Error:
[FAILED] in [SynchronizedBeforeSuite] - /go/src/github.com/opendatahub-io/modelmesh-serving/fvt/helpers.go:439 @ 06/25/25 16:19:34.265 [SynchronizedBeforeSuite] [FAILED] [52.262 seconds] [SynchronizedBeforeSuite] /go/src/github.com/opendatahub-io/modelmesh-serving/fvt/predictor/predictor_suite_test.go:34 [FAILED] Timed out before deployments were ready: map[modelmesh-serving-mlserver-1.x:false modelmesh-serving-ovms-1.x:false modelmesh-serving-torchserve-0.x:false modelmesh-serving-triton-2.x:false] Expected <bool>: false to be true In [SynchronizedBeforeSuite] at: /go/src/github.com/opendatahub-io/modelmesh-serving/fvt/helpers.go:439 @ 06/25/25 16:19:34.265 ------------------------------

Summary by CodeRabbit

  • Tests
    • Increased the waiting period for stable deployment state in the predictor test suite, improving reliability in test setup.

@red-hat-konflux
Copy link

red-hat-konflux bot commented Jun 25, 2025

Caution

There are some errors in your PipelineRun template.

PipelineRun Error
template no kind "TriggerTemplate" is registered for version "tekton.dev/v1beta1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:83"
binding no kind "TriggerBinding" is registered for version "tekton.dev/v1beta1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:83"
listener no kind "EventListener" is registered for version "tekton.dev/v1beta1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:83"

@coderabbitai
Copy link

coderabbitai bot commented Jun 25, 2025

Walkthrough

The timeout for the WaitForStableActiveDeployState function in the predictor test suite setup was increased from 45 seconds to 100 seconds. A log statement indicating the new timeout was added, and the previous 45-second call was commented out.

Changes

File(s) Change Summary
fvt/predictor/predictor_suite_test.go Increased deployment wait timeout from 45s to 100s; added log message

Poem

A timeout grew, from forty-five to one hundred,
While waiting for states, our patience unblundered.
With a log to declare, "TIMEOUT 100" in sight,
Deployments can linger deep into the night.
🕰️🐇

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Signed-off-by: Mariah Holder <marholde@redhat.com>
Copy link

@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.

Actionable comments posted: 0

🧹 Nitpick comments (3)
fvt/predictor/predictor_suite_test.go (3)

59-59: Remove commented code instead of leaving it in place.

Commented-out code should be removed rather than left in the codebase, as version control already tracks the previous implementation.

-	//WaitForStableActiveDeployState(time.Second * 45)

60-60: Improve log message clarity.

The current log message "TIMEOUT 100" is not descriptive enough. Consider making it more informative about what is happening.

-	Log.Info("TIMEOUT 100")
+	Log.Info("Waiting for stable deployment state with increased timeout of 100 seconds")

61-61: Consider using a named constant for the timeout value.

The timeout change from 45 to 100 seconds addresses the CI deployment readiness issues as intended. However, consider extracting the timeout value into a named constant for better maintainability.

+const deploymentStabilityTimeout = 100 * time.Second
+
 // ... later in the function
-	WaitForStableActiveDeployState(time.Second * 100)
+	WaitForStableActiveDeployState(deploymentStabilityTimeout)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c25e59a and 2e42739.

📒 Files selected for processing (1)
  • fvt/predictor/predictor_suite_test.go (1 hunks)

Copy link
Member

@andresllh andresllh left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Jun 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andresllh, mholder6

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-merge-bot openshift-merge-bot bot merged commit a543e2c into opendatahub-io:main Jun 25, 2025
8 checks passed
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.

2 participants