summary refs log tree commit diff
path: root/src/tools
AgeCommit message (Collapse)AuthorLines
2018-02-11Delete executables if the test ran successfully.Mark Simulacrum-3/+5
This isn't a perfect heuristic, but since the amount of run-fail tests is far lower than run-pass tests for now, it should be sufficient to ensure that we don't run into CI limits. This makes it possible to run the test binary manually (e.g., under gdb/lldb) if it failed to attempt to find out why.
2018-02-11compiletest: Delete the executable immediately after running.kennytm-2/+8
This should save a lot of space on musl test cases (whose standard library are linked statically).
2018-02-01Update Cargo on betaAlex Crichton-0/+0
2018-01-18Update cargo on beta.Eric Huss-0/+0
2018-01-10Shorten names of some compiler generated artifacts.Michael Woerister-0/+4
2018-01-10Try to fix a perf regression by updating logMalo Jaffré-1/+1
Upgrade `log` to `0.4` in multiple crates.
2018-01-01Ignore remaining broken links caused by rustdoc bugsMalo Jaffré-2/+20
As pointed out by @ollie27.
2018-01-01Update crates and submodules to pull doc fixesMalo Jaffré-0/+0
Update `rand` crate to `0.3.19`. Update `log` crate to `0.3.9` and `0.4.1`. Update `parking_lot_core` crate to `0.2.9`. Upgrade all flate2 dependencies to `1.0.1`. - Update `rust-installer` submodule.
2018-01-01Auto merge of #47064 - kennytm:force-trailing-newlines, r=estebankbors-0/+11
Add a tidy check for missing or too many trailing newlines. I've noticed recently there are lots of review comments requesting to fix trailing newlines. If this is going to be an official style here, it's better to let the CI do this repetitive check.
2017-12-31Update cargoFelix Schütt-0/+0
2017-12-30Add a tidy check to ensure all files have 1 or 2 trailing newlines.kennytm-0/+11
2017-12-29Update rustfmt to 0.3.4Igor Matuszewski-19/+5
2017-12-28Update RLSIgor Matuszewski-0/+0
2017-12-26Auto merge of #46554 - ↵bors-54/+121
kennytm:45861-step-4-5-6-7-upload-test-result-and-remove-toolstate-toml, r=alexcrichton [auto-toolstate] Upload the toolstate result to an external git repository, and removes BuildExpectation This PR consists of 3 commits. 1. (Steps 4–6) The `toolstate.json` output previously collected is now pushed to the https://github.com/rust-lang-nursery/rust-toolstate repository. 2. (Step 7) Revert commit ab018c7, thus removing all traces of `BuildExpectation` and `toolstate.toml`. 3. (Step 8) Adjust CONTRIBUTION.md for the new procedure. These are the last steps of #45861. After this PR, the toolstate will be automatically computed and published to https://rust-lang-nursery.github.io/rust-toolstate/. There is no need to manage toolstate.toml again. Closes #45861.
2017-12-27Clarify toolstate names. Move publish.py to a more convenient location.kennytm-0/+105
2017-12-27Revert "Add a file to trivially disable tool building or testing"kennytm-36/+0
This reverts commit ab018c76e14b87f3c9e0b7384cc9b02d94779cd5. This also adds the `ToolBuild::is_ext_tool` field to replace the previous `ToolBuild::expectation` field, to indicate whether a build-failure of certain tool is essential.
2017-12-27cargo update and add miri as the rustc workspace member.kennytm-18/+16
2017-12-26Rollup merge of #46940 - EdSchouten:cloudabi, r=alexcrichtonkennytm-2/+6
Add support for CloudABI targets to the rustc backend. CloudABI is a sandboxed UNIX-like runtime environment. It is a programming environment that uses a capability-based security model. In practice this means that many POSIX interfaces are present, except for ones that try to access resources out of thin air. For example, open() is gone, but openat() is present. Right now I'm at the point where I can compile very basic CloudABI applications on all four supported architectures (ARM and x86, 32 and 64 bits). The next step will be to get libstd to work. Patches for that are outside the scope of this change. More info: https://nuxi.nl/cloudabi/ https://github.com/NuxiNL/cloudlibc/
2017-12-24Update Cargo and its dependenciesAlex Crichton-0/+0
Just a routine update!
2017-12-22Add CloudABI to the list of supported targets.Ed Schouten-2/+6
Backend definitions for these targets are present, meaning we can start announcing this target. While there, sort the list alphabetically.
2017-12-22Auto merge of #46732 - estebank:silence-recovered-blocks, r=petrochenkovbors-1/+1
Do not emit type errors on recovered blocks When a parse error occurs on a block, the parser will recover and create a block with the statements collected until that point. Now a flag stating that a recovery has been performed in this block is propagated so that the type checker knows that the type of the block (which will be identified as `()`) shouldn't be checked against the expectation to reduce the amount of irrelevant diagnostic errors shown to the user. Fix #44579.
2017-12-21Mark clippy as brokenEsteban Küber-1/+1
2017-12-22Rollup merge of #46636 - frewsxcv:frewsxcv-fn-box, r=estebankkennytm-1/+1
Replace libtest/lib.rs:FnBox with std::boxed::FnBox. Fixes https://github.com/rust-lang/rust/issues/41810.
2017-12-21Auto merge of #46531 - cramertj:no-mo-modrs, r=nikomatsakisbors-3/+4
Implement non-mod.rs mod statements Fixes https://github.com/rust-lang/rust/issues/45385, cc https://github.com/rust-lang/rust/issues/44660 This will fail tidy right now because it doesn't recognize my UI tests as feature-gate tests. However, I'm not sure if compile-fail will work out either because compile-fail usually requires there to be error patterns in the top-level file, which isn't possible with this feature. What's the recommended way to handle this?
2017-12-20Rollup merge of #46751 - michaelwoerister:c-incremental, r=alexcrichtonkennytm-1/+1
incr.comp.: Add `-C incremental` in addition to `-Z incremental` This PR adds a stable commandline option for invoking incremental compilation. r? @alexcrichton
2017-12-19Break rlsTaylor Cramer-1/+1
2017-12-19Break rustfmtTaylor Cramer-1/+1
2017-12-19Implement non-mod.rs mod statementsTaylor Cramer-1/+2
2017-12-18incr.comp.: Add -Cincremental in addition to -ZincrementalMichael Woerister-1/+1
2017-12-17Auto merge of #46436 - eddyb:unpacked, r=arielb1,oli-obkbors-1/+1
Detect unaligned fields via `aggregate.align < field.align`, instead of a `packed` flag. Closes #46423. cc @oli-obk
2017-12-17Mark miri as broken.Eduard-Mihai Burtescu-1/+1
2017-12-17Add sync module to rustc_data_structuresJohn Kåre Alsaker-0/+1
2017-12-16Auto merge of #46743 - oli-obk:miri, r=eddybbors-18/+18
Some miri cleanups r? @eddyb
2017-12-15Allow easily creating cheap eval context instancesOliver Schneider-18/+18
2017-12-15Replace libtest/lib.rs:FnBox with std::boxed::FnBox.Corey Farwell-1/+1
Fixes https://github.com/rust-lang/rust/issues/41810.
2017-12-15Update the rls and rustfmt submodulesOliver Schneider-16/+16
2017-12-15Auto merge of #46641 - petrochenkov:nohelp2, r=nikomatsakisbors-1/+5
Move compile-fail tests with NOTE/HELP annotations to UI Remove NOTE/HELP annotations from UI tests cc https://github.com/rust-lang/rust/issues/44844 @oli-obk @est31 r? @nikomatsakis
2017-12-14Auto merge of #45047 - durka:trait-alias, r=petrochenkovbors-0/+1
trait alias infrastructure This will be an implementation of trait aliases (RFC 1733, #41517). Progress so far: - [x] Feature gate - [x] Add to parser - [x] `where` clauses - [x] prohibit LHS type parameter bounds via AST validation https://github.com/rust-lang/rust/pull/45047#discussion_r143575575 - [x] Add to AST and HIR - [x] make a separate PathSource for trait alias contexts https://github.com/rust-lang/rust/pull/45047#discussion_r143353932 - [x] Stub out enough of typeck and resolve to just barely not ICE Postponed: - [ ] Actually implement the alias part - [ ] #21903 - [ ] #24010 I need some pointers on where to start with that last one. The test currently does this: ``` error[E0283]: type annotations required: cannot resolve `_: CD` --> src/test/run-pass/trait-alias.rs:34:16 | 34 | let both = foo(); | ^^^ | = note: required by `foo` ```
2017-12-14Support regexes in custom normalization in UI testsVadim Petrochenkov-1/+5
2017-12-14rls depends on rustfmtAlex Burka-0/+1
2017-12-14Auto merge of #45002 - oli-obk:miri, r=eddybbors-6/+24
Validate miri against the HIR const evaluator r? @eddyb cc @alexcrichton @arielb1 @RalfJung The interesting parts are the last few functions in `librustc_const_eval/eval.rs` * We warn if miri produces an error while HIR const eval does not. * We warn if miri produces a value that does not match the value produced by HIR const eval * if miri succeeds and HIR const eval fails, nothing is emitted, but we still return the HIR error * if both error, nothing is emitted and the HIR const eval error is returned So there are no actual changes, except that miri is forced to produce the same values as the old const eval. * This does **not** touch the const evaluator in trans at all. That will come in a future PR. * This does **not** cause any code to compile that didn't compile before. That will also come in the future It would be great if someone could start a crater run if travis passes
2017-12-14Move mir validation out of treeOliver Schneider-5/+21
2017-12-14Use PathBuf instead of String where applicableOliver Schneider-2/+2
2017-12-12Move large chunks of miri from rustc::mir::interpret to rustc_mir::interpretOliver Schneider-0/+1
2017-12-11Merge remote-tracking branch 'origin/master' into miriOliver Schneider-767/+1189
2017-12-10Imply must-compile-successfully in ui-tests when the run-pass flag is present.Tommy Ip-4/+6
2017-12-10Enforce successful ui tests to have must-compile-successfully flag.Tommy Ip-7/+11
2017-12-07Auto merge of #46532 - est31:master, r=est31bors-4/+6
Allow feature-gate tests to live in ui/ and migrate most of the tests from compile-fail The PR consists of three commits: 1. change tidy to allow feature-gate tests to live in ui/ 2. migrate some feature gate tests to ui/ with renaming only 3. migrate some feature gate tests to ui/ with also removing `// gate-test-...` lines and renaming them to the standard `feature-gate-<feat-name>.rs` format.
2017-12-07extend MIR dump with detailed, extra informationNiko Matsakis-3/+8
2017-12-07Tidy: allow feature-gate tests to be ui testsest31-4/+6
ui tests are the future, especially since the recent improvement where we have gained checking and requiring of //~ERROR comments. The tidy feature-gate test check is intended to be 50% an actual insurance that there is a check, and 50% to be a teacher that such checks are required. With this commit applied, newbies might interpret stuff wrongly and create tests that don't fail but succeed instead. This is not what feature gate tests are for though. Therefore, in a later step, when only ui tests are allowed to be feature gate tests, we will add checking to ensure that a file marked as gate test is actually required to be a compilation failure. Right now implementing such a check is a bit annoying as one needs to only do it when the compile-fail test is in the ui test suite :/.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-03 18:48:10 +0000