summary refs log tree commit diff
path: root/src/test/run-fail
AgeCommit message (Collapse)AuthorLines
2016-09-12typeck: use NoExpectation to check return type of diverging fnAlex Burka-0/+1
This fixes #35849, a regression introduced by the typeck refactoring around TyNever/!.
2016-08-13Add explanations to testsAndrew Cann-0/+12
2016-08-13Permit `! as T` with testAndrew Cann-0/+18
2016-08-13Add tests for ! typeAndrew Cann-0/+81
2016-08-13Add some tests for ! typeAndrew Cann-0/+26
2016-08-13Rename empty/bang to neverAndrew Cann-3/+1
Split Ty::is_empty method into is_never and is_uninhabited
2016-08-13Control usage of `!` through a feature gate.Andrew Cann-0/+1
Adds the `bang_type` feature gate. `!` in a non-return-type position now relies on that feature.
2016-08-13Add run-fail/adjust_empty.rs testAndrew Cann-0/+18
2016-08-04Update wording on E0080Shantanu Raj-17/+17
Change "attempted" to "attempt"
2016-06-07Rollup merge of #33897 - srinivasreddy:runfail_rustfmt, r=nrcSteve Klabnik-107/+278
run rustfmt on test/run-fail folder
2016-06-06run rustfmt on test/run-fail folderSrinivas Reddy Thatiparthy-107/+278
2016-06-05trans: use the same messages for both MIR and old arithmetic checks.Eduard Burtescu-15/+15
2016-06-05Enable the overflow-related tests for MIRJames Miller-32/+0
2016-06-04Auto merge of #33622 - arielb1:elaborate-drops, r=nikomatsakisbors-0/+47
[MIR] non-zeroing drop This enables non-zeroing drop through stack flags for MIR. Fixes #30380. Fixes #5016.
2016-06-04fix translation of terminators in MSVC cleanup blocksAriel Ben-Yehuda-0/+3
MSVC requires unwinding code to be split to a tree of *funclets*, where each funclet can only branch to itself or to to its parent. Luckily, the code we generates matches this pattern. Recover that structure in an analyze pass and translate according to that.
2016-06-03Auto merge of #33803 - WiSaGaN:feature/rename-main-thread, r=alexcrichtonbors-18/+18
Rename main thread from "<main>" to "main". Fix issue #33789 We may need to discuss whether this counts as a breaking change since code may check the main thread name against "\<main\>". Discussion is in #33789
2016-06-03implement drop elaborationAriel Ben-Yehuda-0/+44
Fixes #30380
2016-05-30std: Clean out old unstable + deprecated APIsAlex Crichton-9/+12
These should all have been deprecated for at least one cycle, so this commit cleans them all out.
2016-05-22Rename main thread from "<main>" to "main".Wangshan Lu-18/+18
Fix issue #33789
2016-03-17Add #[rustc_no_mir] to make tests pass with -Z orbit.Eduard Burtescu-0/+66
2016-03-03Auto merge of #32007 - nikomatsakis:compiletest-incremental, r=alexcrichtonbors-0/+43
This PR extends compiletest to support **test revisions** and with a preliminary **incremental testing harness**. run-pass, compile-fail, and run-fail tests may be tagged with ``` // revisions: a b c d ``` This will cause the test to be re-run four times with `--cfg {a,b,c,d}` in turn. This means you can write very closely related things using `cfg`. You can also configure the headers/expected-errors by writing `//[foo] header: value` or `//[foo]~ ERROR bar`, where `foo` is the name of your revision. See the changes to `coherence-cow.rs` as a proof of concept. The main point of this work is to support the incremental testing harness. This PR contains an initial, unused version. The code that uses it will land later. The incremental testing harness compiles each revision in turn, and requires that the revisions have particular names (e.g., `rpass2`, `cfail3`), which tell it whether a particular revision is expected to compile or not. Two questions: - Is there compiletest documentation anywhere I can update? - Should I hold off on landing the incremental testing harness until I have the code to exercise it? (That will come in a separate PR, still fixing a few details) r? @alexcrichton cc @rust-lang/compiler <-- new testing capabilities
2016-03-02add a run-fail meta testNiko Matsakis-0/+43
2016-02-24Fix testsSimonas Kazlauskas-21/+25
2016-02-24Add some tests for dynamic droppingSimonas Kazlauskas-0/+123
2016-02-17MSVC SEH in MIR is implemented hereSimonas Kazlauskas-4/+0
2016-02-06Ignore a test on MSVCSimonas Kazlauskas-0/+2
The MSVC SEH is still not implemented, so we go ahead and ignore it.
2016-02-04Translation part of drop panic recoverySimonas Kazlauskas-0/+34
With this commit we now finally execute all the leftover drops once some drop panics for some reason!
2016-01-29Get tests working on MSVC 32-bitAlex Crichton-0/+10
2016-01-06Add testsSimonas Kazlauskas-0/+277
2015-12-23Implement custom panic handlersSteven Fackler-0/+64
2015-12-08add tests for ensuring const indexing does not cause compile-time errors in ↵Oliver Schneider-0/+37
runtime code
2015-10-28Move test file to run-fail, since it does an unwrapNiko Matsakis-0/+28
2015-10-13implement RFC 1229Oliver Schneider-39/+20
const eval errors outside of true constant enviroments are not reported anymore, but instead forwarded to a lint.
2015-10-08typos: fix a grabbag of typos all over the placeCristi Cobzarenco-1/+1
2015-09-13Add test for overflowing powPeter Reid-0/+16
This would catch regressions of issue #28012.
2015-08-17Fix existing tests for new `#[repr(simd)]`.Huon Wilson-236/+0
2015-08-12Remove all unstable deprecated functionalityAlex Crichton-92/+0
This commit removes all unstable and deprecated functions in the standard library. A release was recently cut (1.3) which makes this a good time for some spring cleaning of the deprecated functions.
2015-06-20Support checked Shl/Shr on SIMD typesDavid Stygstra-0/+236
2015-06-14Auto merge of #26071 - petrochenkov:assert1, r=alexcrichtonbors-1/+1
`assert_eq!` has better diagnostics than `assert!` and is more helpful when something actually breaks, but the diagnostics has it's price - `assert_eq!` generate some formatting code which is slower to compile and possibly run. [My measurements](https://internals.rust-lang.org/t/assert-a-b-or-assert-eq-a-b/1367/12?u=petrochenkov) show that presence of this formatting code doesn't affect compilation + execution time of the test suite significantly, so `assert_eq!` can be used instead of `assert!` consistently. (Some tests doesn't reside in src/test, they are not affected by these changes, I'll probably open a separate PR for them later)
2015-06-13Auto merge of #26249 - steveklabnik:remove_extern_panic, r=alexcrichtonbors-52/+0
This test has an interesting history, because of fail -> panic. It was originally called extern-fail.rs: https://github.com/rust-lang/rust/commits/master/src/test/run-fail/extern-fail.rs It lived for a while, but was disabled in August 2013: https://github.com/rust-lang/rust/commit/ce95b01014391f29a655d165d9e6d31449ceb835 As you can see, that failure was not specific to this test, however, this code does stuff with the runtime, which was removed. Given that it hasn't even been able to compile in a long time, we should just remove it. r? @brson
2015-06-13Use `assert_eq!` instead of `assert!` in testspetrochenkov-1/+1
2015-06-13Auto merge of #26253 - steveklabnik:remove_old_ignored_tests, r=brsonbors-114/+0
Two commits here: one which removes a bunch of tests, and re-enables a few that work. Second updates the syntax of one of the failing tests. It still doesn't pass, but at least it compiles.
2015-06-12ignore-test cleanupSteve Klabnik-114/+0
Most of these are old, but some specific messages for specific tests: * trait-contravariant-self.rs: failed due to a soundess hole: https://github.com/rust-lang/rust/commit/05e3248a7974f55b64f75a2483b37ff8c001a4ff * process-detatch: https://github.com/rust-lang/rust/commit/15966c3c1f99810ac81053769651776a67181dae says "this test is being ignored until signals are implemented" That's not happening for a long time, and when it is, we'll write tests for it. * deep-vector{,2}.rs: "too big for our poor macro infrastructure", and has been ignored over a year. * borrowck-nested-calls.rs's FIXME #6268 was closed in favor of rust-lang/rfcs#811 * issue-15167.rs works properly now * issue-9737.rs works properly now * match-var-hygiene.rs works properly now Addresses a chunk of #3965
2015-06-12Remove old runtime panic testSteve Klabnik-52/+0
This test has an interesting history, because of fail -> panic. It was originally called extern-fail.rs: https://github.com/rust-lang/rust/commits/master/src/test/run-fail/extern-fail.rs It lived for a while, but was disabled in August 2013: https://github.com/rust-lang/rust/commit/ce95b01014391f29a655d165d9e6d31449ceb835 As you can see, that failure was not specific to this test, however, this code does stuff with the runtime, which was removed. Given that it hasn't even been able to compile in a long time, we should just remove it.
2015-06-12Remove ignored test for #2061Steve Klabnik-26/+0
This test was added on Nov 1, 2012: https://github.com/rust-lang/rust/commit/0069bd2f4612b744ab3731b4c1db13c2f3202185#diff-b516ff69faf8886c48e6f5e833c2548c and then ignored on the same day: https://github.com/rust-lang/rust/commit/a90020fe8dd8be8615df82e6294408bfed82a767#diff-b516ff69faf8886c48e6f5e833c2548c and never unignored again.
2015-05-09Fix the tests broken by replacing `task` with `thread`Barosl Lee-1/+1
2015-05-09Squeeze the last bits of `task`s in documentation in favor of `thread`Barosl Lee-5/+5
An automated script was run against the `.rs` and `.md` files, subsituting every occurrence of `task` with `thread`. In the `.rs` files, only the texts in the comment blocks were affected.
2015-04-26Move qquote.rs from run-fail to run-fail-fulldepsRyan Prichard-44/+0
2015-04-26Remove FakeExtCtxt from qquote tests.Geoffry Song-28/+15
Instead create an ExtCtxt structure.
2015-04-25`qquote-2.rs` -> `run-fail/qquote.rs`Tamir Duberstein-0/+57
Re-enables the test.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-26 17:30:14 +0000