about summary refs log tree commit diff
path: root/src/test/ui
AgeCommit message (Collapse)AuthorLines
2022-09-23Rollup merge of #102134 - flba-eb:master, r=bjorn3Matthias Krüger-62/+6
Detect panic strategy using `rustc --print cfg` Instead of relying on a command line parameter, detect if a target is able to unwind or not. Ignore tests that require unwinding on targets that don't support it. I did not find any place where the removed parameter has been used, but it feels a bit risky as I'm new to this test framework. r? bjorn3
2022-09-23fix testb-naber-35/+6
2022-09-23add testb-naber-0/+67
2022-09-23Auto merge of #102165 - matthiaskrgr:rollup-n5oquhe, r=matthiaskrgrbors-16/+248
Rollup of 8 pull requests Successful merges: - #100734 (Split out async_fn_in_trait into a separate feature) - #101664 (Note if mismatched types have a similar name) - #101815 (Migrated the rustc_passes annotation without effect diagnostic infrastructure) - #102042 (Distribute rust-docs-json via rustup.) - #102066 (rustdoc: remove unnecessary `max-width` on headers) - #102095 (Deduplicate two functions that would soon have been three) - #102104 (Set 'exec-env:RUST_BACKTRACE=0' in const-eval-select tests) - #102112 (Allow full relro on powerpc64-unknown-linux-gnu) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2022-09-23Repair stderr test result to added lineFlorian Bartels-1/+1
2022-09-23Report diagnostics at the actually actionable siteOli Scherer-11/+38
2022-09-23ignore test cases when checking emscriptenFlorian Bartels-0/+2
2022-09-23Some test cleanupsOli Scherer-14/+6
2022-09-23Make the test actually show the problematic caseOli Scherer-19/+19
2022-09-23Show errors instead of hiding them due to an earlier errorOli Scherer-15/+61
2022-09-23Showcase a broken diagnosticOli Scherer-4/+4
2022-09-23Adapt test resultsFlorian Bartels-6/+5
2022-09-23Restore ignore tagFlorian Bartels-57/+0
This test case actually requires std::process.
2022-09-23Auto merge of #100488 - khyperia:invalid-calling-convention-help-message, ↵bors-2/+45
r=nagisa,jyn514 Improve the help message for an invalid calling convention Fixes https://github.com/rust-lang/rust/issues/93601 I mostly followed the suggestions of `@nagisa` in that issue, ~~however, I wasn't sure how to check stability for the suggestion of "Do not suggest CCs that cannot be used due to them being unstable and feature not being enabled", so I did not implement that point.~~ I haven't contributed to rustc much, please feel free to point out suggestions! For example, the `.map(|s| Symbol::intern(s)).collect::<Vec<_>>()` seems pretty gross performance-wise, but maybe that's OK in error reporting code.
2022-09-23Rollup merge of #102104 - Aaron1011:no-test-backtrace, r=Mark-SimulacrumMatthias Krüger-2/+4
Set 'exec-env:RUST_BACKTRACE=0' in const-eval-select tests This allows the tests to pass even if the user has RUST_BACKTRACE set when running 'x.py'
2022-09-23Rollup merge of #101664 - mejrs:similarity, r=fee1-deadMatthias Krüger-0/+132
Note if mismatched types have a similar name If users get a type error between similarly named types, it will point out that these are actually different types, and where they were defined.
2022-09-23Rollup merge of #100734 - ComputerDruid:afit_feature, r=compiler-errorsMatthias Krüger-14/+112
Split out async_fn_in_trait into a separate feature PR #101224 added support for async fn in trait desuraging behind the `return_position_impl_trait_in_trait` feature. Split this out so that it's behind its own feature gate, since async fn in trait doesn't need to follow the same stabilization schedule.
2022-09-23Auto merge of #101708 - compiler-errors:issue-101696, r=jackh726bors-0/+36
Normalize closure signature after construction Astconv can't normalize inputs or outputs with escaping bound vars ([see this](https://doc.rust-lang.org/nightly/nightly-rustc/src/rustc_typeck/check/fn_ctxt/mod.rs.html#294)), so normalize them after we've wrapped them in a binder. Fixes #101696
2022-09-23Serialize RPITIT values in libsMichael Goulet-0/+20
2022-09-22Improve the help message for an invalid calling conventionkhyperia-2/+45
2022-09-22Calculate ProjectionTy::trait_def_id correctlyMichael Goulet-0/+59
2022-09-22Revert "Auto merge of #101620 - cjgillot:compute_lint_levels_by_def, r=oli-obk"Camille GILLOT-74/+19
This reverts commit 2cb9a65684dba47c52de8fa938febf97a73e70a9, reversing changes made to 750bd1a7ff3e010611b97ee75d30b7cbf5f3a03c.
2022-09-23Fix slight issues with stderrRageking8-2/+3
2022-09-23Change UI test stderrRageking8-4/+3
2022-09-22recover from struct nested in structRageking8-0/+17
2022-09-22Auto merge of #102139 - Dylan-DPC:rollup-ljlipt8, r=Dylan-DPCbors-4/+4
Rollup of 8 pull requests Successful merges: - #101598 (Update rustc's information on Android's sanitizers) - #102036 (Remove use of `io::ErrorKind::Other` in std) - #102037 (Make cycle errors recoverable) - #102069 (Skip `Equate` relation in `handle_opaque_type`) - #102076 (rustc_transmute: fix big-endian discriminants) - #102107 (Add missing space between notable trait tooltip and where clause) - #102119 (Fix a typo “pararmeter” in error message) - #102131 (Added which number is computed in compute_float.) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2022-09-22Rollup merge of #102119 - steffahn:fix-pararmeter, r=dtolnayDylan DPC-4/+4
Fix a typo “pararmeter” in error message Issue reported on IRLO: https://internals.rust-lang.org/t/fixing-a-typo/17427
2022-09-22Auto merge of #100980 - compiler-errors:normalize-opaque-w-bound-vars, r=lcnrbors-20/+1
Normalize opaques w/ bound vars First, we reenable normalization of opaque types with escaping late bound regions to fix rust-lang/miri#2433. This essentially reverts #89285. Second, we mitigate the perf regression found in #88862 by simplifying the way that we relate (sub and eq) GeneratorWitness types. This relies on the fact that we construct these GeneratorWitness types somewhat particularly (with all free regions found in the witness types replaced with late bound regions) -- but those bound regions really should be treated as existential regions, not universal ones. Those two facts leads me to believe that we do not need to use the full `higher_ranked_sub` machinery to relate two generator witnesses. I'm pretty confident that this is correct, but I'm glad to discuss this further.
2022-09-22resolve: Set effective visibilities for imports more preciselyVadim Petrochenkov-2/+2
Instead of setting them for all primary and additional IDs of the import, only set them for the binding's true ID.
2022-09-22effective visibility: Add test for a reexport of two namesVadim Petrochenkov-2/+45
in different namespaces, one public and another private.
2022-09-22Auto merge of #100982 - fee1-dead-contrib:const-impl-requires-const-trait, ↵bors-174/+248
r=oli-obk Require `#[const_trait]` on `Trait` for `impl const Trait` r? `@oli-obk`
2022-09-21Split out async_fn_in_trait into a separate featureDan Johnson-14/+112
PR #101224 added support for async fn in trait desuraging behind the return_position_impl_trait_in_trait feature. Split this out so that it's behind its own feature gate, since async fn in trait doesn't need to follow the same stabilization schedule.
2022-09-22Optimize subtyping and equation of GeneratorWitnessMichael Goulet-20/+1
2022-09-22Rollup merge of #102084 - andrewpollack:add-issue-panic-unwind, r=bjorn3Yuki Okushi-2/+3
Adding needs-unwind for test using panic::catch_unwind Adding needs-unwind for test using panic::catch_unwind cc. `@djkoloski` r? `@tmandry`
2022-09-22Rollup merge of #102073 - andrewpollack:add-execvp-call-ignore, r=tmandryYuki Okushi-0/+1
Adding ignore fuchsia tests for execvp Adding ignore fuchsia tests for execvp cc. ``@djkoloski`` r? ``@tmandry``
2022-09-22Rollup merge of #102071 - andrewpollack:add-needs-unwind-for-binary-size, ↵Yuki Okushi-0/+3
r=tmandry Adding needs-unwind for tests testing memory size of Futures/Closures Adding needs-unwind for tests testing memory size of Futures/Closures cc. ``@djkoloski`` r? ``@tmandry``
2022-09-22Rollup merge of #102033 - andrewpollack:add-unwind-on-pretty, r=tmandryYuki Okushi-0/+3
Adding needs-unwind to nicer-assert-messages compiler ui tests Tests where unwind is required for asserting on contents of error message cc. ``@djkoloski`` r? ``@tmandry``
2022-09-22Rollup merge of #102032 - andrewpollack:bad-signal-compiler-tests, r=tmandryYuki Okushi-0/+5
Adding ignore fuchsia tests for signal interpretation cases Tests where Signal interpreting is required. Since Fuchsia currently does not return signals of type `libc::SIGSEGV` etc., instead, use generalized `!status.success()` case. cc. `@djkoloski` r? `@tmandry`
2022-09-22Bless test output changesFrank Steffahn-4/+4
2022-09-21Auto merge of #102097 - Dylan-DPC:rollup-gc75oh4, r=Dylan-DPCbors-4/+51
Rollup of 7 pull requests Successful merges: - #89891 (`alloc`: add unstable cfg features `no_rc` and `no_sync`) - #101995 (Add another example for `uN::carrying_mul`) - #102031 (Adding ignore fuchsia tests for Backtrace, ErrorKind cases) - #102041 (Improve `-Zmeta-stats` some more) - #102045 (fix ConstProp handling of written_only_inside_own_block_locals) - #102058 (Clarify Path::extension() semantics in docs abstract) - #102059 (Use rebind instead of dummy binder in `SameTypeModuloInfer` relation) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2022-09-21Adding ignore fuchsia tests for signal casesAndrew Pollack-0/+5
2022-09-21Set 'exec-env:RUST_BACKTRACE=0' in const-eval-select testsAaron Hill-2/+4
This allows the tests to pass even if the user has RUST_BACKTRACE set when running 'x.py'
2022-09-21Make error messages great again (and fix clippy and add test)Deadbeef-42/+64
2022-09-21Rollup merge of #102059 - compiler-errors:issue-101984, r=jackh726Dylan DPC-0/+41
Use rebind instead of dummy binder in `SameTypeModuloInfer` relation Lazy binder usage (sorry, my fault) + assertion in `Binder::dummy` Fixes #101984
2022-09-21Rollup merge of #102031 - andrewpollack:compiler-tests-backtrace, r=tmandryDylan DPC-4/+10
Adding ignore fuchsia tests for Backtrace, ErrorKind cases Tests where Backtrace parses are required (invalid since Fuchsia backtraces are not symbolized), and test where ErrorKind is not properly translated from a Fuchsia-style to Unix-style error code cc. ```@djkoloski``` r? ```@tmandry```
2022-09-21Improve diagnostic for adding more bounds to opaque typesOli Scherer-4/+6
2022-09-21Reproduce sad diagnosticOli Scherer-0/+35
2022-09-21Simplify insert_outlives_predicate opaque type logicOli Scherer-0/+8
2022-09-21Add regression testOli Scherer-0/+18
2022-09-21Also collect bounds from the ParamEnv for opaque typesOli Scherer-13/+2