Skip to content

OLS-2385: removing temperature param and pass threshold. - #2932

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
sriroopar:fix_threshold_temp
Aug 12, 2026
Merged

OLS-2385: removing temperature param and pass threshold.#2932
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
sriroopar:fix_threshold_temp

Conversation

@sriroopar

@sriroopar sriroopar commented May 15, 2026

Copy link
Copy Markdown
Contributor

Description

gpt 5 mini doesnt support temperature param, removing it temporarily and removing threshold, as only 50 percent of evals are passing in ci

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change

Related Tickets & Documents

  • Related Issue #
  • Closes #

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Summary by CodeRabbit

  • Evaluation Updates

    • Reduced the maximum judge response length to 512 tokens across evaluation configurations.
    • Removed explicit temperature settings from judge configurations, including troubleshooting evaluations.
  • Testing

    • Periodic evaluations now print consolidated summaries with token usage details.
    • Failed evaluations include brief diagnostics and up to three error reasons.
    • Pass criteria now require at least one successful evaluation instead of enforcing an error-rate limit.

@openshift-ci
openshift-ci Bot requested review from joshuawilson and raptorsun May 15, 2026 18:10
@sriroopar
sriroopar force-pushed the fix_threshold_temp branch from 5434039 to fa4409f Compare May 15, 2026 19:35
@sriroopar
sriroopar force-pushed the fix_threshold_temp branch from fa4409f to 2c14818 Compare July 13, 2026 15:56
@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 111f6ce7-7382-4dd9-8ffc-7f3dd4d28bf4

📥 Commits

Reviewing files that changed from the base of the PR and between 9a2d421 and a47bc3b.

📒 Files selected for processing (7)
  • eval/system_azure_openai_lseval.yaml
  • eval/system_openai_lseval.yaml
  • eval/system_rhelai_vllm_lseval.yaml
  • eval/system_rhoai_vllm_lseval.yaml
  • eval/system_watsonx_lseval.yaml
  • eval/troubleshooting/system.yaml
  • tests/e2e/evaluation/test_lseval_periodic.py
💤 Files with no reviewable changes (1)
  • eval/troubleshooting/system.yaml
🚧 Files skipped from review as they are similar to previous changes (5)
  • eval/system_watsonx_lseval.yaml
  • eval/system_openai_lseval.yaml
  • eval/system_azure_openai_lseval.yaml
  • eval/system_rhoai_vllm_lseval.yaml
  • eval/system_rhelai_vllm_lseval.yaml

📝 Walkthrough

Walkthrough

Judge LLM configurations now use a 512-token limit where configured and omit temperature settings. Periodic LSEval validation prints consolidated diagnostics and requires at least one successful evaluation instead of enforcing an error-rate threshold.

Changes

LSEval configuration and validation

Layer / File(s) Summary
Judge configuration updates
eval/system_*_lseval.yaml, eval/troubleshooting/system.yaml
Judge configurations reduce max_tokens from 4096 to 512 where applicable and remove temperature settings.
Periodic evaluation result validation
tests/e2e/evaluation/test_lseval_periodic.py
Periodic runs print consolidated evaluation and judge-token diagnostics and assert that at least one evaluation passed instead of applying a fixed error-rate limit.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: joshuawilson, raptorsun

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately identifies the removal of the temperature parameter and evaluation pass threshold, which are the main changes.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ 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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
tests/e2e/evaluation/test_lseval_periodic.py (1)

192-208: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Consider renaming passed to non_errored for clarity.

passed = total - errors includes both passing and failing (non-error) evaluations, not just passing ones. The assertion message "zero successful results" correctly conveys the intent, but the variable name passed is misleading since some of those results may have failed without erroring.

♻️ Suggested rename
-    passed = total - errors
+    non_errored = total - errors

And update the print/assertion references accordingly:

-        f"Total={total}  Passed={passed}  Errors={errors}  "
+        f"Total={total}  Non-errored={non_errored}  Errors={errors}  "
-    assert passed > 0, f"All {total} evaluations errored — zero successful results."
+    assert non_errored > 0, f"All {total} evaluations errored — zero successful results."
🤖 Prompt for 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.

In `@tests/e2e/evaluation/test_lseval_periodic.py` around lines 192 - 208, Rename
the local variable passed to non_errored in the evaluation summary, preserving
its calculation as total minus errors. Update every corresponding print and
assertion reference so the summary accurately labels non-error evaluations
rather than successful results.
🤖 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.

Nitpick comments:
In `@tests/e2e/evaluation/test_lseval_periodic.py`:
- Around line 192-208: Rename the local variable passed to non_errored in the
evaluation summary, preserving its calculation as total minus errors. Update
every corresponding print and assertion reference so the summary accurately
labels non-error evaluations rather than successful results.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 91e29b64-7a65-48ce-bfaa-335a533bfa1f

📥 Commits

Reviewing files that changed from the base of the PR and between 6578cfb and 2c14818.

📒 Files selected for processing (7)
  • eval/system_azure_openai_lseval.yaml
  • eval/system_openai_lseval.yaml
  • eval/system_rhelai_vllm_lseval.yaml
  • eval/system_rhoai_vllm_lseval.yaml
  • eval/system_watsonx_lseval.yaml
  • eval/troubleshooting/system.yaml
  • tests/e2e/evaluation/test_lseval_periodic.py
💤 Files with no reviewable changes (1)
  • eval/troubleshooting/system.yaml

@sriroopar sriroopar changed the title removing temperature param and pass threshold. OLS-2385: removing temperature param and pass threshold. Jul 13, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 13, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 13, 2026

Copy link
Copy Markdown

@sriroopar: This pull request references OLS-2385 which is a valid jira issue.

Details

In response to this:

Description

gpt 5 mini doesnt support temperature param, removing it temporarily and removing threshold, as only 50 percent of evals are passing in ci

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change

Related Tickets & Documents

  • Related Issue #
  • Closes #

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Summary by CodeRabbit

  • Evaluation Updates

  • Standardized judge evaluation settings with a 512-token response limit.

  • Updated troubleshooting evaluations to use the OpenAI gpt-5-mini model.

  • Removed explicit temperature settings from judge configurations.

  • Testing

  • Evaluation runs now provide consolidated results and judge-token diagnostics.

  • Periodic evaluation checks require at least one successful evaluation instead of enforcing a fixed error-rate threshold.

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.

@sriroopar
sriroopar force-pushed the fix_threshold_temp branch from 2c14818 to 207512d Compare July 22, 2026 12:49

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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 `@tests/e2e/evaluation/test_lseval_periodic.py`:
- Around line 197-202: Update the judge_detail selection near
overall.get("total_judge_llm_tokens", -1) so missing or negative
total_judge_llm_tokens values report “unavailable,” while zero retains the
failed-before-judge message and positive values retain “judge was called.”
🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 36993db0-506c-45e5-8e18-1abe4b3b6b82

📥 Commits

Reviewing files that changed from the base of the PR and between 2c14818 and 207512d.

📒 Files selected for processing (7)
  • eval/system_azure_openai_lseval.yaml
  • eval/system_openai_lseval.yaml
  • eval/system_rhelai_vllm_lseval.yaml
  • eval/system_rhoai_vllm_lseval.yaml
  • eval/system_watsonx_lseval.yaml
  • eval/troubleshooting/system.yaml
  • tests/e2e/evaluation/test_lseval_periodic.py
💤 Files with no reviewable changes (1)
  • eval/troubleshooting/system.yaml
🚧 Files skipped from review as they are similar to previous changes (5)
  • eval/system_rhoai_vllm_lseval.yaml
  • eval/system_openai_lseval.yaml
  • eval/system_rhelai_vllm_lseval.yaml
  • eval/system_watsonx_lseval.yaml
  • eval/system_azure_openai_lseval.yaml

Comment on lines +197 to +202
judge_tokens = overall.get("total_judge_llm_tokens", -1)
judge_detail = (
"0 → OLS calls failed before judge was reached"
if judge_tokens == 0
else "judge was called"
)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Handle unavailable judge-token data separately.

When total_judge_llm_tokens is missing, the fallback -1 is treated as evidence that the judge was called because only 0 selects the failure message. Report negative or missing values as “unavailable” instead.

🤖 Prompt for 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.

In `@tests/e2e/evaluation/test_lseval_periodic.py` around lines 197 - 202, Update
the judge_detail selection near overall.get("total_judge_llm_tokens", -1) so
missing or negative total_judge_llm_tokens values report “unavailable,” while
zero retains the failed-before-judge message and positive values retain “judge
was called.”

@sriroopar
sriroopar force-pushed the fix_threshold_temp branch from 207512d to f06f26f Compare July 28, 2026 15:03
@sriroopar
sriroopar force-pushed the fix_threshold_temp branch from f06f26f to a47bc3b Compare August 6, 2026 13:16
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@sriroopar

Copy link
Copy Markdown
Contributor Author

/retest

@raptorsun

Copy link
Copy Markdown
Contributor

is this still needed?
the description says removing it temporarily

@sriroopar

Copy link
Copy Markdown
Contributor Author

/retest

@sriroopar

Copy link
Copy Markdown
Contributor Author

@raptorsun the change is still reqired as it enables the models without the params to run, it is ready to merge as tests have passed. PTAL :)

@onmete

onmete commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 12, 2026
@openshift-ci

openshift-ci Bot commented Aug 12, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: onmete

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 Aug 12, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit d6779cd into openshift:main Aug 12, 2026
11 of 12 checks passed
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants