-
Notifications
You must be signed in to change notification settings - Fork 103
python 3.11 pytest-reportportal hijacks the fullpath in pytest log output on linux #319
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
Comments
This is the rp_logging.py finction that returns wrong:
|
Here is an errorstack, I catually have no idea where it happened, since rp has hijacked the stack (I believe it is a session timeout for selenium)
|
@fenchu So for python 2.7 - 3.10 everything works correctly, and for 3.11 we suddenly started "hijack" something. No way. Unless someone point me to the code I rather believe this is Python's core library bug. |
@HardNorth sorry for bumping this old issue. I can open a new one on the client repo if you think it'll be more suitable. I'm seeing some strange behavior with python 3.11 as well, and it may indeed be a result of some change in core python, but one that may require a fix in the RP client nevertheless. Please see this issue on cpython for reference: python/cpython#97941 What I'm seeing on reportportal client is that this line is now being returned as the caller: https://github.com/reportportal/client-Python/blob/bd50b91f55f9d8dd9ea0dab649e207562ab3a843/reportportal_client/logs/__init__.py#L65 This is probably a result of the change in cpython, which could potentially explain the "hijacking" described in this ticket too. WDYT? |
Actually, found the exact bug in the client and have a test + fix for it, will open a PR soon. |
python 3.11
pytest-reportportal==5.1.2
On linux the fullpaths always use: rp_logging.py inside pytest testing. We use pyenv in linux and venv in windows:
But on windows it is fine. (It is the same code/same requirements.txt but it runs in linux-container in our CI system (gitlabCI):
All was fine before I upgraded to python 3.11, probably a update to logging.py
The text was updated successfully, but these errors were encountered: