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

pytest warnings in builds #10563

Open
tianyizheng02 opened this issue Oct 15, 2023 · 7 comments
Open

pytest warnings in builds #10563

tianyizheng02 opened this issue Oct 15, 2023 · 7 comments
Labels

Comments

@tianyizheng02
Copy link
Contributor

Repository commit

Doesn't matter

Python version (python --version)

Python 3.12.0, the current version used in builds

Dependencies version (pip freeze)

Doesn't matter

Expected behavior

pytest runs with no (internal) warnings

Actual behavior

Every build (see our Actions tab) has the following warnings:

/opt/hostedtoolcache/Python/3.12.0/x64/lib/python3.12/site-packages/coverage/report_core.py:115: CoverageWarning: Couldn't parse '/home/runner/work/Python/Python/config-3.py': No source for code: '/home/runner/work/Python/Python/config-3.py'. (couldnt-parse)
  coverage._warn(msg, slug="couldnt-parse")
/opt/hostedtoolcache/Python/3.12.0/x64/lib/python3.12/site-packages/coverage/report_core.py:115: CoverageWarning: Couldn't parse '/home/runner/work/Python/Python/config.py': No source for code: '/home/runner/work/Python/Python/config.py'. (couldnt-parse)
  coverage._warn(msg, slug="couldnt-parse")

I don't know what files these are, and I don't know what's causing these warnings to occur.

@SOBAN50
Copy link

SOBAN50 commented Oct 17, 2023

Okay so I spent good time understanding the issue and I have come to the conclusion that it is an issue with the
Python\compression\peak_signal_to_noise_ratio.py file.

It arises due to the cv2 library. cv2 uses a config file for its operations. These files are config-3.py and config.py.
The coverage module considers it a python file for which code coverage has to be checked, but its not actually a Python file but a configuration file. Thats what generates a warning.

@SOBAN50
Copy link

SOBAN50 commented Oct 17, 2023

There are multiple solutions to this:

  • Leave it as it as because its just a warning and does not break any code functionality.
  • Consider using the PILLOW package instead of CV2.

@Saswatsusmoy
Copy link
Contributor

Okay so I spent good time understanding the issue and I have come to the conclusion that it is an issue with the Python\compression\peak_signal_to_noise_ratio.py file.

It arises due to the cv2 library. cv2 uses a config file for its operations. These files are config-3.py and config.py. The coverage module considers it a python file for which code coverage has to be checked, but its not actually a Python file but a configuration file. Thats what generates a warning.

I tried to implement the code without using any external libraries, it seems that the warnings still popup.

@SOBAN50
Copy link

SOBAN50 commented Oct 21, 2023

@Saswatsusmoy I have tried using the code just by commenting out the CV2 part.
No warnings pop up in my case.

@SOBAN50
Copy link

SOBAN50 commented Oct 21, 2023

To reiterate, we are talking about the warnings in the PyTest Code Coverage part.

@pratyakshsuri2003

This comment was marked as off-topic.

@SOBAN50
Copy link

SOBAN50 commented Oct 26, 2023

Okay so I spent good time understanding the issue and I have come to the conclusion that it is an issue with the Python\compression\peak_signal_to_noise_ratio.py file.

It arises due to the cv2 library. cv2 uses a config file for its operations. These files are config-3.py and config.py. The coverage module considers it a python file for which code coverage has to be checked, but its not actually a Python file but a configuration file. Thats what generates a warning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants