Merged
Conversation
There was a problem hiding this comment.
Pull Request Overview
This pull request updates CI testing workflows and baseline score configurations. The changes include:
- Updating the pip installation command in the pr-run-test workflow to install the "full" extra.
- Modifying the daily-run-test workflow to install updated dependencies including replacing torch versions and combining extra installations.
- Renaming baseline score keys in the oc_score_baseline_fullbench YAML file from *_naive_average to *_accuracy.
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/pr-run-test.yml | Updated pip install options to use the "full" extra installation. |
| .github/workflows/daily-run-test.yml | Modified dependency installation steps and updated torch versions. |
| .github/scripts/oc_score_baseline_fullbench.yaml | Renamed baseline score keys for consistency in score reporting. |
Comments suppressed due to low confidence (3)
.github/workflows/pr-run-test.yml:48
- [nitpick] Consider verifying that the '[full]' extra installs all required components without causing dependency conflicts within the CI environment.
python3 -m pip install -e "[full]" --cache-dir ${{env.PIP_CACHE_PATH}}
.github/workflows/daily-run-test.yml:160
- [nitpick] Review whether both 'opencompass[full]' and the subsequent 'opencompass[api]' installations are necessary, as there might be overlapping dependencies between the two extras.
pip install opencompass[full] --cache-dir ${{env.PIP_CACHE_PATH}}
.github/scripts/oc_score_baseline_fullbench.yaml:27
- [nitpick] Ensure that all tools and downstream processes expecting the old '_naive_average' keys are updated to work with the new '_accuracy' key naming convention.
mmlu-other_accuracy: 72.6
stephen-nju
pushed a commit
to stephen-nju/opencompass
that referenced
this pull request
May 14, 2025
* update * update * update * update
zyc140345
pushed a commit
to zyc140345/opencompass
that referenced
this pull request
Oct 23, 2025
* update * update * update * update
iamkaia
pushed a commit
to iamkaia/opencompass
that referenced
this pull request
Feb 4, 2026
* update * update * update * update
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:
After PR: