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

Transport & pytest: garbage cannot be removed [Errno 39] #6751

Open
khsrali opened this issue Feb 10, 2025 · 13 comments
Open

Transport & pytest: garbage cannot be removed [Errno 39] #6751

khsrali opened this issue Feb 10, 2025 · 13 comments
Labels
good first issue Issues that should be relatively easy to fix also for beginning contributors

Comments

@khsrali
Copy link
Contributor

khsrali commented Feb 10, 2025

To reproduce

When running pytest test_all_plugins.py -s, despite all tests passing successful, a long tail of warning messages is printed:

..
  warnings.warn(
/home/**/lib/python3.12/site-packages/_pytest/pathlib.py:95: PytestWarning: (rm_rf) error removing /tmp/pytest-of-khosra_a/garbage-82a5592f-5337-4d9c-934e-7a6ace59c9a7/popen-gw0/remote7
<class 'OSError'>: [Errno 39] Directory not empty: 'remote7'
  warnings.warn(
/home/**/lib/python3.12/site-packages/_pytest/pathlib.py:95: PytestWarning: (rm_rf) error removing /tmp/pytest-of-khosra_a/garbage-82a5592f-5337-4d9c-934e-7a6ace59c9a7/popen-gw0
<class 'OSError'>: [Errno 39] Directory not empty: 'popen-gw0'
  warnings.warn(
/home/**/lib/python3.12/site-packages/_pytest/pathlib.py:95: PytestWarning: (rm_rf) error removing /tmp/pytest-of-khosra_a/garbage-82a5592f-5337-4d9c-934e-7a6ace59c9a7/popen-gw4/remote8
<class 'OSError'>: [Errno 39] Directory not empty: 'remote8'
..

that pytest cannot clean the garbage.

To be investigated. Also pinging @unkcpz

@khsrali khsrali added the good first issue Issues that should be relatively easy to fix also for beginning contributors label Feb 11, 2025
@FARDEEN-785
Copy link

Hey if Its not deleting Why not delete it Manually and then runs the Test

@khsrali
Copy link
Contributor Author

khsrali commented Feb 12, 2025

Because we don't want to do it manually, and because it should not happen. :-)

@FARDEEN-785
Copy link

Because we don't want to do it manually, and because it should not happen. :-)

Can't we can use Force method to delete

@unkcpz
Copy link
Member

unkcpz commented Feb 13, 2025

The issue me relate to pytest-dev/pytest#12381, which may or may not resolved from our side. If someone what to pick this issue, would be nice to have a deep understanding on problem of data racing introduced by pytest-xdist and how to avoid it nicely.

@FARDEEN-785
Copy link

Well I am new to this and don’t have deep understanding but still I will try to resolve this issue

@crs7617
Copy link

crs7617 commented Feb 25, 2025

hello @khsrali , is this issue still open? If yes, can I proceed with this ?

@khsrali
Copy link
Contributor Author

khsrali commented Feb 26, 2025

Hi @crs7617,

I think also @ayushjariyal showed some interest working on this.
I don't know if he's still working on it or not.

@ayushjariyal
Copy link
Contributor

@khsrali I am working on it. Right now, my semester exams are going on, so I am unable to give my full time to this. However, I am trying my best.

@khsrali
Copy link
Contributor Author

khsrali commented Feb 26, 2025

It's all good, no hurry! take your time.

@crs7617
Copy link

crs7617 commented Feb 26, 2025

@khsrali Thanks for the update! if there's anything I can help with, feel free to let me know.

@crs7617
Copy link

crs7617 commented Feb 26, 2025

@khsrali, I noticed that @ayushjariyal is currently working on issue #6728. I just wanted to clarify if issue #6751 is separate from that, or if they are related. If they are distinct, I’d be happy to proceed with #6751. Let me know what you think!

@khsrali
Copy link
Contributor Author

khsrali commented Feb 26, 2025

They are independent issues.
I don't know. Maybe @ayushjariyal should answer, if he's also working on that.
For me, either way is ok.

@crs7617
Copy link

crs7617 commented Feb 26, 2025

alright, thanks for the clarification !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Issues that should be relatively easy to fix also for beginning contributors
Projects
None yet
Development

No branches or pull requests

5 participants