Skip to content

dist(release/1.29): backport patches, pt. 2#4927

Merged
rami3l merged 40 commits into
rust-lang:release/1.29from
rami3l:backport/202606
Jul 2, 2026
Merged

dist(release/1.29): backport patches, pt. 2#4927
rami3l merged 40 commits into
rust-lang:release/1.29from
rami3l:backport/202606

Conversation

@rami3l

@rami3l rami3l commented Jun 29, 2026

Copy link
Copy Markdown
Member

Part of #4862; continuation of #4867.

@rustbot

This comment has been minimized.

@rami3l rami3l force-pushed the backport/202606 branch 4 times, most recently from 2162e8c to 49f5332 Compare June 29, 2026 19:32
@rami3l rami3l requested a review from djc June 29, 2026 19:49
@rami3l rami3l marked this pull request as ready for review June 29, 2026 19:49
@rami3l rami3l added the backport This is an issue which should be backported to the next patch release, or it is a backporting PR. label Jun 29, 2026
@rami3l rami3l force-pushed the backport/202606 branch 2 times, most recently from a07feb8 to 77c3359 Compare June 30, 2026 06:10
@rustbot

rustbot commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different release/1.29 commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

This prevents a random error on Linux when running the test on CI.
Sometimes, even after `fs::copy()` has returned, the executable is still
considered "busy" by the OS, causing the test to fail with:

```rust
Os { code: 26, kind: ExecutableFileBusy, message: "Text file busy" }
```

This change avoids that by using a direct arg0 override instead.
@rami3l

rami3l commented Jul 2, 2026

Copy link
Copy Markdown
Member Author

@djc Just to be sure, do you have more patches to merge before cutting the new release, or I can merge this and start drafting the changelog later this week?

@djc

djc commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

@djc Just to be sure, do you have more patches to merge before cutting the new release, or I can merge this and start drafting the changelog later this week?

I don't have any concrete plans, and I think the release would have been fine without including this refactoring stuff anyway.

@rami3l rami3l merged commit 50cdda9 into rust-lang:release/1.29 Jul 2, 2026
31 checks passed
@rami3l rami3l deleted the backport/202606 branch July 2, 2026 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This is an issue which should be backported to the next patch release, or it is a backporting PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants