about summary refs log tree commit diff
path: root/src/test
AgeCommit message (Collapse)AuthorLines
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-925/+546
2019-04-18Use new `needs-(profiler|sanitizer)-support` compiletest directive to clean ↵Michael Woerister-30/+20
up some run-make tests.
2019-04-18Add codegen test that makes sure PGO instrumentation is emitted as expected.Michael Woerister-0/+20
2019-04-18Prefix PROFILER_SUPPORT and SANITIZER_SUPPORT test env vars with RUSTC_ to ↵Michael Woerister-14/+14
make things clearer.
2019-04-18Update run-make PGO test to new commandline syntax.Michael Woerister-1/+1
2019-04-18Auto merge of #60058 - varkor:const-generics-ty-refactor, r=cramertjbors-0/+14
Make const parameters enforce no variance constraints Fixes https://github.com/rust-lang/rust/issues/60047. Also includes some minor const refactoring for convenience.
2019-04-18Auto merge of #60048 - estebank:issue-54954, r=sanxiynbors-0/+35
Fix ICE on const evaluation of const method Fix #54954.
2019-04-18Auto merge of #60051 - estebank:fn-sugg, r=davidtwcobors-15/+7
Do not mention missing `PartialOrd` impl when involving uncalled fns
2019-04-17Give custom error for E0277 on `?` error caseEsteban Küber-6/+6
2019-04-17Point at try `?` on errors affecting the err match arm of the desugared codeEsteban Küber-6/+6
2019-04-17whitelist rtm x86 cpu featuretyler-1/+2
2019-04-18Add a test for unused const parametersvarkor-0/+14
2019-04-18Rollup merge of #60037 - eddyb:actually-its-param, r=estebankMazdak Farrokhzad-18/+18
Resolve inconsistency in error messages between "parameter" and "variable". The inconsistency was introduced in 104fe1c4db24f860b890dfd25577f23ee111279a (#33619), when a label saying `type variable` was added to an error with a message talking about `type parameters`. Given that `parameter` is far more prevalent when referring to generics in the context of Rust, IMO it should be that in both the message and the label. r? @nikomatsakis or @estebank
2019-04-17Do not mention missing `PartialOrd` impl when involving uncalled fnsEsteban Küber-15/+7
2019-04-17Auto merge of #59527 - matklad:sized-index, r=Centrilbors-0/+23
Add test checking that Index<T: ?Sized> works I've noticed that we have an `Idx: ?Sized` bound on the **index** in the `Index`, which seems strange given that we accept index by value. My guess is that it was meant to be removed in https://github.com/rust-lang/rust/pull/23601, but was overlooked. If I remove this bound, `./x.py src/libstd/ src/libcore/` passes, which means at least that this is not covered by test. I think there's three things we can do here: * run crater with the bound removed to check if there are any regressions, and merge this, to be consistent with other operator traits * run crater, get regressions, write a test for this with a note that "hey, we tried to fix it, its unfixable" * decide, in the light of by-value DSTs, that this is a feature rather than a bug, and add a test cc @rust-lang/libs EDIT: the forth alternative is that there exist a genuine reason why this is the case, but I failed to see it :D
2019-04-17Fix ICE on const evaluation of const methodEsteban Küber-0/+35
2019-04-17add a test for unsized indexAleksey Kladov-0/+23
2019-04-17Resolve inconsistency in error messages between "parameter" and "variable".Eduard-Mihai Burtescu-18/+18
2019-04-17Rollup merge of #59646 - JohnTitor:improve-wording, r=oli-obkMazdak Farrokhzad-18/+19
const fn: Improve wording fixes #59611 This might need discussion. Feel free to close this PR if we don't need to fix.
2019-04-17Rollup merge of #59128 - oli-obk:colorful_json, r=mark-i-m,eddybMazdak Farrokhzad-71/+72
Emit ansi color codes in the `rendered` field of json diagnostics cc @ljedrz Implemented for https://github.com/rust-lang/rust/pull/56595#issuecomment-447645115 (x.py clippy)
2019-04-16Don't test json with color codes on windowsOliver Scherer-53/+54
2019-04-16fixing testsSaleem Jaffer-1/+1
2019-04-16Auto merge of #59769 - RalfJung:compiletest-normalization, r=alexcrichtonbors-8/+89
compiletest normalization: preserve non-JSON lines such as ICEs Currently, every non-JSON line from stderr gets normalized away when compiletest normalizes the output. In particular, ICEs get normalized to the empty output. That does not seem desirable, so this changes normalization to preserve non-JSON lines instead. Also see https://github.com/laumann/compiletest-rs/issues/169: because of that bug, Miri currently *looks* green in the toolstate, but some tests ICE. That same bug is likely no longer present in latest compiletest because the error code gets checked separately, but it still seems like a good idea to also make sure that ICEs are considered stderr output: This change found an accidental user-visible `error!` in CTFE validation (fixed), and a non-deterministic panic when there are two `main` symbols (not fixed, no idea where this comes from). Both got missed before because non-JSON output got ignored.
2019-04-16this panic occurs not just on Windows, normalize it away everywhereRalf Jung-6/+6
2019-04-16Rollup merge of #59993 - euclio:unused-ref-field, r=estebankMazdak Farrokhzad-0/+107
include mode in unused binding suggestion span Fixes #54180.
2019-04-16Rollup merge of #59992 - QuietMisdreavus:static-settings-path, r=GuillaumeGomezMazdak Farrokhzad-0/+4
rustdoc: use --static-root-path for settings.js At the time i was writing https://github.com/rust-lang/docs.rs/pull/332, i noticed that the `settings.js` file that was being loaded was not being loaded from the `--static-root-path`. This PR fixes that so that users on docs.rs can effectively cache this file.
2019-04-16Rollup merge of #59903 - estebank:after-main, r=oli-obkMazdak Farrokhzad-0/+49
Continue evaluating after missing main
2019-04-16Fix testsYuki OKUSHI-18/+19
2019-04-15normalize away some Windows-only panic printingRalf Jung-3/+15
2019-04-15include mode in unused binding suggestion spanAndy Russell-0/+107
2019-04-15Rollup merge of #59978 - ollie27:rustdoc_default, r=QuietMisdreavusMazdak Farrokhzad-15/+62
rustdoc: Remove default keyword from re-exported trait methods Fixes #59977 r? @QuietMisdreavus As this fixes a stable to beta regression, could it be backported?
2019-04-15Rollup merge of #59648 - alex:must-use-result, r=alexcrichtonMazdak Farrokhzad-1/+1
Add must_use annotations to Result::is_ok and is_err Discussed in #59610
2019-04-15use --static-root-path for settings.jsQuietMisdreavus-0/+4
2019-04-15Update testJohn Kåre Alsaker-182/+186
2019-04-15Preallocate BUILTIN_ATTRIBUTES symbols and use a hash map instead of loopingJohn Kåre Alsaker-2/+2
2019-04-14rustdoc: Remove default keyword from re-exported trait methodsOliver Middleton-15/+62
2019-04-14Auto merge of #59335 - Aaron1011:fix/extern-priv-final, r=Aaron1011bors-1/+1
Properly parse '--extern-private' with name and path It turns out that https://github.com/rust-lang/rust/pull/57586 didn't properly parse `--extern-private name=path`. This PR properly implements the `--extern-private` option. I've added a new `extern-private` option to `compiletest`, which causes an `--extern-private` option to be passed to the compiler with the proper path. Part of https://github.com/rust-lang/rust/issues/44663
2019-04-14Rollup merge of #59936 - petrochenkov:confict, r=davidtwcoMazdak Farrokhzad-0/+12
Fix cross-crate visibility of fictive variant constructors After merging https://github.com/rust-lang/rust/pull/59376 I realized that the code in the decoder wasn't entirely correct - we "decoded" fictive variant constructors with their variant's visibility, which could be public, rather than demoted to `pub(crate)`. Fictive constructors are not directly usable in expression/patterns, but the effect still can be observed with imports. r? @davidtwco
2019-04-14Rollup merge of #59896 - estebank:dedup-spans, r=davidtwcoMazdak Farrokhzad-0/+27
Remove duplicated redundant spans Fix #59895.
2019-04-14Rollup merge of #59877 - Zoxc:hiridify_def_id, r=eddybMazdak Farrokhzad-3/+3
HirIdify hir::Def cc @ljedrz r? @oli-obk
2019-04-14Address review commentsVadim Petrochenkov-0/+3
2019-04-14Fix cross-crate visibility of fictive variant constructorsVadim Petrochenkov-0/+9
2019-04-14huge-enum also exhibits this errorRalf Jung-0/+4
2019-04-14some more tests need normalizationRalf Jung-0/+12
2019-04-14normalize away spurious errorRalf Jung-3/+27
2019-04-14normalize flags and rustc version in ICE reproRalf Jung-2/+4
2019-04-14fix output test for backtrace-debuginfo.rsRalf Jung-2/+4
2019-04-14fix testsRalf Jung-0/+25
2019-04-14Update testsJohn Kåre Alsaker-3/+3
2019-04-14Auto merge of #59798 - rchaser53:issue-59488, r=estebankbors-0/+115
Improvement for comparision against fn I try to add error message. related: https://github.com/rust-lang/rust/issues/59488
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 17:39:54 +0000