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

Rollup of 8 pull requests #127261

Merged
merged 17 commits into from
Jul 3, 2024
Merged

Rollup of 8 pull requests #127261

merged 17 commits into from
Jul 3, 2024

Conversation

jhpratt
Copy link
Member

@jhpratt jhpratt commented Jul 3, 2024

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

tgross35 and others added 17 commits June 19, 2024 19:31
Rearrange the sections and add an example to
`core::hint::assert_unchecked`.
Make both `hint_assert_unchecked` and `const_hint_assert_unchecked`
stable as `hint_assert_unchecked`.
…d, r=dtolnay

Stabilize `hint::assert_unchecked`

Make the following API stable, including const:

```rust
// core::hint, std::hint

pub const unsafe fn assert_unchecked(p: bool);
```

This PR also reworks some of the documentation and adds an example.

Tracking issue: rust-lang#119131
FCP: rust-lang#119131 (comment). The docs update should resolve the remaining concern.
…, r=lcnr

Actually report normalization-based type errors correctly for alias-relate obligations in new solver

We have some special casing to report type mismatch errors that come from projection predicates, but we don't do that for alias-relate obligations. This PR implements that. There's a bit of code duplication, but 🤷

Best reviewed without whitespace.

r? lcnr
…ssible-temp-dir-resolution, r=jieyouxu

Disable rmake test `inaccessible-temp-dir` on riscv64

In rust-lang#126279 the `inaccessible-temp-dir` test was moved to rmake, I followed up with a 'fix' derived from rust-lang#126355 in rust-lang#126707.

That 'fix' was misguided and hiding the true issue of the linker being incorrect for `riscv64gc-unknown-linux-gnu` (addressed in rust-lang#126916).

Unfortunately, even with the linker fixed, this test doesn't work. I asked myself why this appeared to work on other platforms and investigated why. Both the containers for `armhf-gnu` and `riscv64gc` run their tests as `root` and have `NO_CHANGE_USER` set:

https://github.com/rust-lang/rust/blob/553a69030e5a086eb3841d020db8c9c463948c72/src/ci/docker/host-x86_64/disabled/riscv64gc-gnu/Dockerfile#L99

This means the tests are run as `root`. As `root`, it's perfectly normal and reasonable to violate permission checks this way:

```bash
$ sudo mkdir scratch
$ sudo chmod o-w scratch
$ sudo mkdir scratch/backs
$
```

Because of this, this PR makes the test ignored on `riscv64gc` for now.

As an alternative, I believe the best long-term strategy would be to not run the tests as `root` for this job.

## Testing

> [!NOTE]
> `riscv64gc-unknown-linux-gnu` is a [**Tier 2 with Host Tools** platform](https://doc.rust-lang.org/beta/rustc/platform-support.html), all tests may not necessarily pass! This change should only ignore `inaccessible-temp-dir` and not affect other tests.

You can test out the job locally:

```sh
mv src/ci/docker/host-x86_64/disabled/riscv64gc-gnu src/ci/docker/host-x86_64/riscv64gc-gnu
DEPLOY=1 ./src/ci/docker/run.sh riscv64gc-gnu
```
… r=lqd,ChrisDenton

unreferenced-used-static: run test everywhere

Follow-up to rust-lang#127099.
…h_not, r=jhpratt

Stabilize atomic_bool_fetch_not

closes rust-lang#98485

`@rustbot` modify labels: +T-libs-api
remove unnecessary ignore-endian-big from stack-overflow-trait-infer …

Follow-up to [this](rust-lang#122895 (comment)) discussion
Add a test for `generic_const_exprs`

Fixes rust-lang#103770

r? ``@Nilstrieb``
…ient-has-longer-timeout, r=Mark-Simulacrum

Give remote-test-client a longer timeout

In rust-lang#126959, ``@Mark-Simulacrum`` suggested we simply extend the timeout of the `remote-test-client` instead of making it configurable. This is acceptable for my use case.

I'm doing some work with a remote host running tests using `x.py`'s remote test runner system.

After building the `remote-test-server` with:

```bash
./x build src/tools/remote-test-server --target aarch64-unknown-linux-gnu
```

I can transfer the `remote-test-server` to the remote and set up a port forwarded SSH connection, then I run:

```bash
TEST_DEVICE_ADDR=127.0.0.1:12345 ./x.py test library/core --target aarch64-unknown-linux-gnu
```

This works great if the host is nearby, however if the average round trip time is over 100ms (the timeout), it creates problems as it silently trips the timeout.

This PR extends that timeout to a less strict 2s.

r? ``@Mark-Simulacrum``
@rustbot rustbot added A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc 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. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) rollup A PR which is a rollup labels Jul 3, 2024
@jhpratt
Copy link
Member Author

jhpratt commented Jul 3, 2024

@bors r+ rollup=never p=8

@bors
Copy link
Contributor

bors commented Jul 3, 2024

📌 Commit d801730 has been approved by jhpratt

It is now in the queue for this repository.

@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 Jul 3, 2024
@bors
Copy link
Contributor

bors commented Jul 3, 2024

⌛ Testing commit d801730 with merge 2db4ff4...

@bors
Copy link
Contributor

bors commented Jul 3, 2024

☀️ Test successful - checks-actions
Approved by: jhpratt
Pushing 2db4ff4 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jul 3, 2024
@bors bors merged commit 2db4ff4 into rust-lang:master Jul 3, 2024
7 checks passed
@rustbot rustbot added this to the 1.81.0 milestone Jul 3, 2024
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#123588 Stabilize hint::assert_unchecked ed7adf002c5b48c5d5491e2f120831dc8aaa809a (link)
#126403 Actually report normalization-based type errors correctly f… b8ff71ac03970e738bcc3a9fa0bf663440c667a9 (link)
#126917 Disable rmake test inaccessible-temp-dir on riscv64 58954dad242ba75be9fb21edd2fac8aa3e535234 (link)
#127115 unreferenced-used-static: run test everywhere 16303ae99facec3b5a442778b739b9599924d1f6 (link)
#127204 Stabilize atomic_bool_fetch_not 711275c81a2c8634662a42448162f831686adb48 (link)
#127239 remove unnecessary ignore-endian-big from stack-overflow-tr… 5ede03e15ecaeef877273bcdcbb282abde2f5e25 (link)
#127245 Add a test for generic_const_exprs a202924fc21f970a85cad8d18521e82f38eaef99 (link)
#127246 Give remote-test-client a longer timeout e783239f6ff361838cf44cc14ce76529e50ebbb0 (link)

previous master: d68fe4eaa8

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (2db4ff4): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (secondary 3.4%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
3.4% [2.2%, 4.5%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 696.734s -> 695.82s (-0.13%)
Artifact size: 327.74 MiB -> 327.73 MiB (-0.00%)

@jhpratt jhpratt deleted the rollup-cpoayvr branch July 13, 2024 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc 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. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants