about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2016-03-03 17:41:13 +0000
committerbors <bors@rust-lang.org>2016-03-03 17:41:13 +0000
commit493d999ffa44be6610441dabab80e18dda90015a (patch)
tree1e8cb7a3a287236d5a56363f4f62d2f9bf0c7f94 /src/libstd/sys/unix/stack_overflow.rs
parentf6e125f04a54ec65eac0ecd3cb68e180210a06fa (diff)
parentfc4d0ecf20103e6f394e8771d11373e15ce70501 (diff)
downloadrust-493d999ffa44be6610441dabab80e18dda90015a.tar.gz
rust-493d999ffa44be6610441dabab80e18dda90015a.zip
Auto merge of #32007 - nikomatsakis:compiletest-incremental, r=alexcrichton
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
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions