Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xfails for OV 2025.0 #3257

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from
Open

Conversation

KodiaqQ
Copy link
Collaborator

@KodiaqQ KodiaqQ commented Feb 6, 2025

Changes

  • Added xfails for the known issues with OV 2025.0

Reason for changes

  • Robust CI

Related tickets

  • 161230

Tests

  • nightly/job/test_examples/670 - passed
  • nightly/job/TriggerBetta/967 - passed

@KodiaqQ KodiaqQ changed the title XFails for OV 2025.0 Xfails for OV 2025.0 Feb 6, 2025
@github-actions github-actions bot added the NNCF PT Pull requests that updates NNCF PyTorch label Feb 6, 2025
@KodiaqQ
Copy link
Collaborator Author

KodiaqQ commented Feb 6, 2025

@openvinotoolkit/nncf-maintainers, can someone review this, please? Thanks.

@KodiaqQ KodiaqQ marked this pull request as ready for review February 6, 2025 13:11
@KodiaqQ KodiaqQ requested a review from a team as a code owner February 6, 2025 13:11
@@ -265,6 +265,7 @@
"backend": "openvino",
"requirements": "examples/llm_compression/openvino/smollm2_360m_fp8/requirements.txt",
"cpu": "Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz",
"xfail_reason": "FP8 output regression - CVS-161459",
Copy link
Contributor

Choose a reason for hiding this comment

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

My opinion, that all examples have to work. Please set the previous openvino version in the requirements.txt for this example.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

In this case, we should remove non-working examples, since we claim the full support of the concrete OpenVINO version in our docs.
Also, this would not work for the next release if the original issue would not be fixed.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

In any case, this example works, since there are no problems observed from the side of the NNCF API or quantization scheme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NNCF PT Pull requests that updates NNCF PyTorch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants