Skip to content

os.remove on Windows could fail if files are still in use #554

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

Closed
wants to merge 1 commit into from

Conversation

kshitiz305
Copy link

Description

Closes #535

Checklist

  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

Copy link
Contributor

copy-pr-bot bot commented Apr 10, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

# unrelated to the test session about to start.
pass
yield
# No cleanup needed after yield anymore
Copy link
Collaborator

Choose a reason for hiding this comment

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

That's a great move.

What do you think about adding something like this?

import logging

logger = logging.getLogger(__name__)

...

        except PermissionError as e:
            logger.warning(f"Could not remove file {f!r}: {e}")

That way, if a file is in use unexpectedly, we’ll at least have breadcrumbs.

We should probably also log the FileNotFoundError.

Comment on lines 58 to 61
@pytest.fixture(scope="session", autouse=True)
def clean_up_cffi_files():
yield
# Clean up files from previous runs before the session starts
files = glob.glob(os.path.join(os.getcwd(), "_cpu_obj*"))
Copy link
Collaborator

Choose a reason for hiding this comment

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

Because of issues like the Windows cleanup issue, would highly recommend using pytest's builtin temporary directory management fixtures

This will handle all the directory creation and cleanup for us with less fuss

Copy link
Collaborator

Choose a reason for hiding this comment

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

+1 — if we have the free bandwidth

Copy link
Collaborator

Choose a reason for hiding this comment

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

Simpler, more reliable cleanup of the test directory will lead to bandwidth savings in the long term ;)

Copy link
Member

Choose a reason for hiding this comment

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

I've explained this in a past group meeting, repeating here for wider visibility. pytest fixtures like tmp_path etc unfortunately do not work. The temp files are generated by CFFI inside a code sample (here), and we have no way to influence where it places the modules (without making the code sample overly complicated) I am afraid. I'd be happy to be proven wrong!

@kkraus14
Copy link
Collaborator

@kshitiz305 unfortunately, at this time we are unable to accept code contributions as mentioned in https://github.com/NVIDIA/cuda-python/blob/main/CONTRIBUTING.md. Based on this I am going to close this PR.

We hope to change this in the future.

@kkraus14 kkraus14 closed this Apr 11, 2025
@leofang
Copy link
Member

leofang commented May 5, 2025

We hope to change this in the future.

Hi @kshitiz305, a quick update: We've recently opened up for external contributions to cuda.core after changing its license to Apache 2.0 (#583). If you're still interested in pushing this PR through the finish line, feel free to reopen it! 🙂

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

Successfully merging this pull request may close these issues.

os.remove on Windows could fail if files are still in use
5 participants