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.

Sign up for GitHub

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

Jump to bottom

Text file busy #1353

Open
smoelius opened this issue Sep 28, 2024 · 3 comments
Open

Text file busy #1353

smoelius opened this issue Sep 28, 2024 · 3 comments

Comments

@smoelius
Copy link
Collaborator

From here:

│   Error: Could not copy `/tmp/.tmprPqqvF/target/debug/dylint_driver-nightly-2024-09-05-x86_64-unknown-linux-gnu` to `/home/runner/.dylint_drivers/nightly-2024-09-05-x86_64-unknown-linux-gnu/dylint-driver`
│   
│   Caused by:
│       Text file busy (os error 26)

This PR could be helpful as a reference: alloy-rs/svm-rs#140
@smoelius
Copy link
Collaborator Author

smoelius commented Oct 3, 2024

Fixed by 4438f40

@smoelius smoelius closed this as completed Oct 3, 2024
@smoelius
Copy link
Collaborator Author

smoelius commented Oct 3, 2024

The fix requires a release. Reopening until then.

@smoelius smoelius reopened this Oct 3, 2024
@smoelius
Copy link
Collaborator Author

smoelius commented Oct 7, 2024

I'm still seeing "Text file busy" errors.

Examples:

My current (unconfirmed) theory is that Cargo/rustc is trying to overwrite a dynamic library while it is being executed.

@smoelius smoelius changed the title Could not copy /tmp/.../dylint-driver-... to /home/runner/.dylint_drivers/.../dylint-driver Text file busy Oct 7, 2024
@smoelius smoelius pinned this issue Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@smoelius