Skip to content

Fix Speculative decoding test cases#288

Closed
vaibhavjainwiz wants to merge 3 commits intoopendatahub-io:mainfrom
vaibhavjainwiz:fix_spec_dec
Closed

Fix Speculative decoding test cases#288
vaibhavjainwiz wants to merge 3 commits intoopendatahub-io:mainfrom
vaibhavjainwiz:fix_spec_dec

Conversation

@vaibhavjainwiz
Copy link
Copy Markdown
Member

@vaibhavjainwiz vaibhavjainwiz commented May 5, 2025

Description

How Has This Been Tested?

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Summary by CodeRabbit

  • Chores
    • Updated command-line arguments for speculative decoding configuration to use a single JSON string, simplifying the way parameters are provided.

@vaibhavjainwiz vaibhavjainwiz requested a review from a team as a code owner May 5, 2025 05:48
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented May 5, 2025

## Walkthrough

The changes update two test files for speculative decoding in model serving. Previously, multiple command-line arguments were used to configure speculative decoding parameters. These have now been consolidated into a single `--speculative_config` argument, which accepts a JSON string encoding all relevant parameters. This affects how the configuration is passed to the serving runtime but does not alter the underlying test logic or exported entities.

## Changes

| File(s)                                                                                          | Change Summary                                                                                                         |
|-------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_draft.py        | Replaces separate command-line flags for speculative decoding with a single `--speculative_config` JSON argument.     |
| tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_ngram.py        | Consolidates three separate speculative decoding flags into one JSON-based `--speculative_config` argument.            |

## Poem

> In the warren of code, where arguments roam,  
> Now JSON config brings them all home.  
> No more flags to scatter or lose,  
> Just one string for all you choose!  
> A hop, a skip, one config to bind—  
> Speculative rabbits, streamlined!  
> 🐇

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cc0a1f1 and 39314d0.

📒 Files selected for processing (2)
  • tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_draft.py (1 hunks)
  • tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_ngram.py (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_ngram.py
  • tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_draft.py
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 5, 2025

The following are automatically added/executed:

  • PR size label.
  • Run pre-commit
  • Run tox
  • Add PR author as the PR assignee

Available user actions:

  • To mark a PR as WIP, add /wip in a comment. To remove it from the PR comment /wip cancel to the PR.
  • To block merging of a PR, add /hold in a comment. To un-block merging of PR comment /hold cancel.
  • To mark a PR as approved, add /lgtm in a comment. To remove, add /lgtm cancel.
    lgtm label removed on each new commit push.
  • To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
    verified label removed on each new commit push.
  • To Cherry-pick a merged PR /cherry-pick <target_branch_name> to the PR. If <target_branch_name> is valid,
    and the current PR is merged, a cherry-picked PR would be created and linked to the current PR.
Supported labels

{'/wip', '/hold', '/lgtm', '/verified'}

Copy link
Copy Markdown
Contributor

@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 (2)
tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_draft.py (1)

20-20: Consolidation of speculative decoding parameters looks good.

The change to consolidate separate speculative decoding parameters into a single JSON-structured config improves consistency and alignment with modern configuration approaches.

For improved maintainability, consider defining the speculative config as a Python dictionary first, then converting to JSON string:

-    '--speculative_config={"model": "/mnt/models/granite-7b-instruct-accelerator","num_speculative_tokens": 5}',
+    # Configuration for speculative decoding (draft model)
+    f'--speculative_config={json.dumps({
+        "model": "/mnt/models/granite-7b-instruct-accelerator",
+        "num_speculative_tokens": 5
+    })}',

Don't forget to add import json at the top of the file if you implement this suggestion.

tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_ngram.py (1)

20-20: Consolidation of speculative decoding parameters looks good.

The change to consolidate three separate parameters into a single JSON config is consistent with the similar change in the draft test file and improves the configuration approach.

For improved maintainability, consider defining the speculative config as a Python dictionary first, then converting to JSON string:

-    '--speculative_config={"model": "ngram","num_speculative_tokens": 5, "prompt_lookup_max": 4}',
+    # Configuration for speculative decoding (ngram model)
+    f'--speculative_config={json.dumps({
+        "model": "ngram",
+        "num_speculative_tokens": 5,
+        "prompt_lookup_max": 4
+    })}',

Don't forget to add import json at the top of the file if you implement this suggestion.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 560f952 and cc0a1f1.

📒 Files selected for processing (2)
  • tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_draft.py (1 hunks)
  • tests/model_serving/model_runtime/vllm/speculative_decoding/test_granite_7b_lab_ngram.py (1 hunks)

mwaykole
mwaykole previously approved these changes May 5, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented May 5, 2025

Caution

No docstrings were generated.

Raghul-M
Raghul-M previously approved these changes May 5, 2025
@vaibhavjainwiz vaibhavjainwiz dismissed stale reviews from Raghul-M and mwaykole via b3718d1 May 5, 2025 09:02
"--dtype=float16",
"--speculative-model=/mnt/models/granite-7b-instruct-accelerator",
"--num-speculative-tokens=5",
'--speculative_config={"model": "/mnt/models/granite-7b-instruct-accelerator", "num_speculative_tokens": 5}',
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
'--speculative_config={"model": "/mnt/models/granite-7b-instruct-accelerator", "num_speculative_tokens": 5}',
"--speculative_config",
"{"model": "/mnt/models/granite-7b-instruct-accelerator","num_speculative_tokens": 5}",

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@tarukumar
There is something wrong with the pre-commit hook configured on opendatahub-tests repo. I had made all changes as per your suggestion but pre-commit hook make a new commit on my PR and change the value.
39314d0

@vaibhavjainwiz
Copy link
Copy Markdown
Member Author

create new PR : #294

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.

5 participants