diff options
| author | bors <bors@rust-lang.org> | 2016-05-16 14:41:50 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2016-05-16 14:41:50 -0700 |
| commit | cd6a400175cc230008a5094a8bbb44a3794f0465 (patch) | |
| tree | bbddcde08c131f5dd1f3ba58eb5c1dfcb5d0b3ab /src/rustllvm/RustWrapper.cpp | |
| parent | 4fdf2c4f976ce52163841ba5b3117bb2bb06d97e (diff) | |
| parent | 24cfa1efb0385ede414d47a4a59f7673045151dc (diff) | |
| download | rust-cd6a400175cc230008a5094a8bbb44a3794f0465.tar.gz rust-cd6a400175cc230008a5094a8bbb44a3794f0465.zip | |
Auto merge of #33588 - nikomatsakis:compiletest-ui, r=acrichto
add UI testing framework This adds a framework for capturing and tracking the precise output of rustc, which allows us to check all manner of minor details with the output. It's pretty strict right now -- the output must match almost exactly -- and hence maybe a bit too strict. But I figure we can add wildcards or whatever later. There is also a script intended to make updating the references easy, though the script could make things a *bit* easier (in particular, it'd be nice if it would find the build directory for you automatically). One thing I was wondering about is the best way to test colors. Since windows doesn't embed those in the output stream, this test framework can't test colors on windows -- so I figure we can just write tests that are ignored on windows and which pass `--color=always` or whatever to rustc. cc @jonathandturner r? @alexcrichton
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
