Rollup of 19 pull requests

[Zalathar]

Successful merges:

• Implement overflow for infinite implied lifetime bounds #138676 (Implement overflow for infinite implied lifetime bounds)
• Make error message for missing fields with .. and without .. more consistent #139024 (Make error message for missing fields with .. and without .. more consistent)
• Tell LLVM about impossible niche tags #139098 (Tell LLVM about impossible niche tags)
• compiler: report error when trait object type param reference self #139124 (compiler: report error when trait object type param reference self)
• Update to new rinja version (askama) #139321 (Update to new rinja version (askama))
• Don't construct preds w escaping bound vars in diagnostic_hir_wf_check #139346 (Don't construct preds w escaping bound vars in diagnostic_hir_wf_check)
• make it possible to use stage0 libtest on compiletest #139386 (make it possible to use stage0 libtest on compiletest)
• Fix trait upcasting to dyn type with no principal when there are projections #139421 (Fix trait upcasting to dyn type with no principal when there are projections)
• Don't call Span::with_parent on the good path in has_stashed_diagnostic #139468 (Don't call Span::with_parent on the good path in has_stashed_diagnostic)
• rm RegionInferenceContext::var_infos #139476 (rm RegionInferenceContext::var_infos)
• Add job summary links to post-merge report #139481 (Add job summary links to post-merge report)
• compiletest: Stricter parsing for diagnostic kinds #139485 (compiletest: Stricter parsing for diagnostic kinds)
• Update some comment/docs related to "extern intrinsic" removal #139490 (Update some comment/docs related to "extern intrinsic" removal)
• Update books #139491 (Update books)
• Revert r-a changes of rust-lang/rust#139455 #139496 (Revert r-a changes of Remove support for extern "rust-intrinsic" blocks #139455)
• document panic behavior of Vec::resize and Vec::resize_with #139500 (document panic behavior of Vec::resize and Vec::resize_with)
• Fix stack overflow in exhaustiveness due to recursive HIR opaque hidden types #139501 (Fix stack overflow in exhaustiveness due to recursive HIR opaque hidden types)
• add missing word in doc comment #139504 (add missing word in doc comment)
• compiletest: Trim whitespace from environment variable names #139507 (compiletest: Trim whitespace from environment variable names)

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[rustbot]

⚠️ Warning ⚠️

• These commits modify submodules.

[Zalathar]

@bors r+ rollup=never p=4

[bors]

📌 Commit 7d32832 has been approved by Zalathar

It is now in the queue for this repository.

[compiler-errors]

@matthiaskrgr: Why did you close a larger rollup seemingly in favor of a rollup of less than half its size?

[matthiaskrgr]

Yes, i saved us from sinking a day or two of ci time into a rollup that is almost guaranteed to fail :)

[compiler-errors]

@matthias: That's not how rollups work. The purpose of a rollup is to test artifacts in parallel. Don't randomly close people's PRs to try to preempt your smaller rollups just because you think it should get merged first.

[compiler-errors]

@bors r+ rollup=never p=10

[bors]

💡 This pull request was already approved, no need to approve it again.

• There's another pull request that is currently being tested, blocking this pull request: Test linking and running no_std binaries #138904

[bors]

📌 Commit 7d32832 has been approved by compiler-errors

It is now in the queue for this repository.

[matthiaskrgr]

If you want to test prs, you should use try-jobs , the way you don't block the queue for a day and and a half

[compiler-errors]

Making myself clear, it doesn't matter if this rollup fails to get merged.

The purpose of a rollup is to make sure that we're always testing artifacts to push things out of the queue.

If you do the math, we'd have to fail basically every rollup for us to really need to incentivize making small rollups, and there are 33 PRs in the queue, so it doesn't really warrant doing that right now.

[compiler-errors]

the way you don't block the queue for a day and and a half

Where are you getting this number from? Testing a rollup takes like three hours.

[matthiaskrgr]

unfortunately, if you rollup 20 prs, and there are 3 bad ones which is quite likely, that will mean you won't push anything out of the queue for around 7 hours, and then you will have 45 waiting in the queue:(

[compiler-errors]

I think things are fine here :) And if this rollup fails, it'll just fall back to the next rollup, so no harm done.

I think it's best not to micromanage other people's rollups without even leaving a comment.

[bors]

⌛ Testing commit 7d32832 with merge 959c2bf...

[rust-log-analyzer]

The job test-various failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

---- [ui] tests/ui/compiletest-self-test/env-trim-name.rs stdout ----

error: test run failed!
status: exit status: 134
command: cd "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/compiletest-self-test/env-trim-name" && MY_EXEC_ENV=" my-exec-value" RUSTC="/checkout/obj/build/x86_64-unknown-linux-gnu/stage2/bin/rustc" RUST_TEST_THREADS="4" "/wasmtime-v19.0.0-x86_64-linux/wasmtime" "run" "-C" "cache=n" "--dir" "." "--env" "RUSTC_BOOTSTRAP" "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/compiletest-self-test/env-trim-name/a.wasm"
stdout: none
--- stderr -------------------------------

thread 'main' panicked at /checkout/tests/ui/compiletest-self-test/env-trim-name.rs:14:5:
assertion `left == right` failed
  left: Err(NotPresent)
 right: Ok(" my-exec-value")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: failed to run main module `/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/compiletest-self-test/env-trim-name/a.wasm`

Caused by:
    0: failed to invoke command default
    1: error while executing at wasm backtrace:
           0: 0x4051 - a.wasm!__rustc[2e92fd3a05a752b4]::__rust_start_panic
           1: 0x3ec2 - a.wasm!__rustc[2e92fd3a05a752b4]::rust_panic
           2: 0x3e95 - a.wasm!std::panicking::rust_panic_with_hook::h5a70ecac66721dfe
           3: 0x2f37 - a.wasm!std::panicking::begin_panic_handler::{{closure}}::h0c38b59cdb955a2a
           4: 0x2ea3 - a.wasm!std::sys::backtrace::__rust_end_short_backtrace::h86bf1a335ca6ce13
           5: 0x3828 - a.wasm!__rustc[2e92fd3a05a752b4]::rust_begin_unwind
           6: 0x8253 - a.wasm!core::panicking::panic_fmt::hc0919c759f330d26
           7: 0x9e79 - a.wasm!core::panicking::assert_failed_inner::h91d603150ebd817c
           8:  0x451 - a.wasm!core::panicking::assert_failed::h851ba26672a84008
           9:  0x52d - a.wasm!env_trim_name::main::h7ec0c8a2ec8aae40
          10:  0x2c7 - a.wasm!std::sys::backtrace::__rust_begin_short_backtrace::he938f4cb913e7d40
          11:  0x2ba - a.wasm!std::rt::lang_start::{{closure}}::h47e476c689a93465
          12: 0x193d - a.wasm!std::rt::lang_start_internal::h3ccbd4867c11502a
          13:  0x566 - a.wasm!__main_void
          14:  0x293 - a.wasm!_start
    2: wasm trap: wasm `unreachable` instruction executed
------------------------------------------



failures:

[bors]

💔 Test failed - checks-actions