Skip to content

Rollup of 7 pull requests #141437

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

Merged
merged 46 commits into from
May 23, 2025
Merged

Rollup of 7 pull requests #141437

merged 46 commits into from
May 23, 2025

Conversation

matthiaskrgr
Copy link
Member

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

ehuss and others added 30 commits May 14, 2025 18:26
This updates some doctests that fail to run on android. We will soon be
supporting cross-compiled doctests, and the `arm-android` job fails to
run these tests.

In summary:
- Android re-exports some traits from linux under a different path.
- Android doesn't seem to have common unix utilities like `true`,
  `false`, or `whoami`, so these are disabled.
Add more comments to libc-fs-with-isolation test
enable clippy::as_conversions to fully rule out as-casts
run tests on mips-unknown-linux-gnu
…ryW-issue

GetUserProfileDirectoryW: reference issue regarding implementation details we rely on
test direct usage of io::{stdout,stderr,stdin}
FileDescription: improve read/write docs
lolbinarycat and others added 10 commits May 22, 2025 12:31
1. rustdoc::bare_urls doesn't output
   invalid suggestions if source_span_for_markdown_range
   fails to find a span

2. source_span_for_markdown_range tries harder to
   return a span by applying an additional diagnostic

fixes rust-lang#135851
…851, r=GuillaumeGomez

Improve handling of rustdoc lints when used with raw doc fragments.

1. `rustdoc::bare_urls` no longer outputs incoherent suggestions if `source_span_for_markdown_range` returns None, instead outputting no suggestion
2. `source_span_for_markdown_range` has one more heuristic, so it will return `None` less often.
3. add ui test to make sure we don't emit nonsense suggestions.

fixes rust-lang#135851
…im-for-error-dropee-fix, r=oli-obk

Async drop poll shim for error dropee generates noop body

Fixes rust-lang#140930.

When dropee type for async drop poll shim is `ty::Error(_)`, the generated poll function will be noop body. To avoid ICE in `elaborate_drop`.
…Mark-Simulacrum

Update std doctests for android

This updates some doctests that fail to run on android. We will soon be supporting cross-compiled doctests, and the `arm-android` job fails to run these tests.

In summary:
- Android re-exports some traits from linux under a different path.
- Android doesn't seem to have common unix utilities like `true`, `false`, or `whoami`, so these are disabled.
…mulacrum

discuss deadlocks in the std::io::pipe() example

I think it's important to discuss deadlocks in examples of how to use pipes. The current example does include an explicit `drop()`, but it also implicitly relies on the fact that the `Command` object is temporary, so that it drops its copy of `pong_tx`. This sort of thing tends to trip people up when they use pipes for the first time. I might've gone overboard with the comments in this version, but I'm curious what folks think.
…InTheVoid

rustdoc JSON: Don't apply `#[repr]` privacy heuristics

Split out from rust-lang#116882.
Context: rust-lang#116882 (comment).
Partially reverts rust-lang#138018.

cc `@obi1kenobi`
r? aDotInTheVoid or rustdoc
…rochenkov

Rename `kw::Empty` as `sym::empty`.

Because the empty string is not a keyword.

r? `@petrochenkov`
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-rustdoc-json Area: Rustdoc JSON backend S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels May 23, 2025
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented May 23, 2025

📌 Commit ee1768c has been approved by matthiaskrgr

It is now in the queue for this repository.

@bors
Copy link
Collaborator

bors commented May 23, 2025

🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 23, 2025
@bors
Copy link
Collaborator

bors commented May 23, 2025

⌛ Testing commit ee1768c with merge e88e854...

@bors
Copy link
Collaborator

bors commented May 23, 2025

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing e88e854 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label May 23, 2025
@bors bors merged commit e88e854 into rust-lang:master May 23, 2025
7 checks passed
@rustbot rustbot added this to the 1.89.0 milestone May 23, 2025
Copy link

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 163cb4e (parent) -> e88e854 (this PR)

Test differences

Show 28 test diffs

Stage 1

  • [rustdoc-json] tests/rustdoc-json/attrs/repr_transparent.rs: pass -> [missing] (J0)
  • [ui] tests/rustdoc-ui/lints/bare-urls-limit.rs: [missing] -> pass (J0)
  • [ui] tests/ui/async-await/async-drop/open-drop-error2.rs: [missing] -> pass (J0)

Stage 2

  • [rustdoc-json] tests/rustdoc-json/attrs/repr_transparent.rs: pass -> [missing] (J1)
  • [ui] tests/rustdoc-ui/lints/bare-urls-limit.rs: [missing] -> pass (J1)
  • [ui] tests/ui/async-await/async-drop/open-drop-error2.rs: [missing] -> pass (J2)

Additionally, 22 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard e88e85463468ce5d5ce468414eb69e3b15fa8d42 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. dist-apple-various: 5421.2s -> 6893.4s (27.2%)
  2. x86_64-apple-1: 10951.4s -> 9208.3s (-15.9%)
  3. dist-x86_64-apple: 8739.4s -> 9908.2s (13.4%)
  4. dist-i686-linux: 6755.6s -> 6091.4s (-9.8%)
  5. i686-gnu-nopt-1: 9113.2s -> 8259.8s (-9.4%)
  6. dist-aarch64-apple: 6107.0s -> 5543.9s (-9.2%)
  7. mingw-check: 1349.7s -> 1246.2s (-7.7%)
  8. x86_64-rust-for-linux: 2531.8s -> 2709.2s (7.0%)
  9. dist-aarch64-msvc: 8661.0s -> 8145.0s (-6.0%)
  10. x86_64-mingw-1: 8672.6s -> 9129.2s (5.3%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-attributes Area: Attributes (`#[…]`, `#![…]`) A-rustdoc-json Area: Rustdoc JSON backend merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.