This repository was archived by the owner on Oct 25, 2024. It is now read-only.
remove optimum-intel version limit #1651
Merged
Conversation
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
Signed-off-by: changwangss <[email protected]>
⚡ Required checks status: All passing 🟢Groups summary🟢 Optimize Unit Test workflow
These checks are required after the changes to Thank you for your contribution! 💜
|
13 tasks
|
Could you help to check why the CI itrex version is 0.1.dev1+xxxx? the expection is 1.6.dev+xxxxx, please fix. |
chensuyue
force-pushed
the
wangchang/optimum-intel
branch
from
a98b85f to
369977b
Compare
chensuyue
approved these changes
Jul 4, 2024
yiliu30
approved these changes
Jul 4, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Type of Change
feature or bug fix or documentation or others
API changed or not
Description
detail description
JIRA ticket: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed