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>2015-02-08 12:35:03 +0000
committerbors <bors@rust-lang.org>2015-02-08 12:35:03 +0000
commit725cc06464abda7a657780f12feaefb7f10333c6 (patch)
tree85f5b24268b66ed67c3de3a6897d93c1d2d7771c /src/libstd/sys/unix/stack_overflow.rs
parentd4a66e9b098e3c322161f0397e932cf6d3c1b15c (diff)
parent01db9a46af72383811f39091be70e9721aaa159a (diff)
downloadrust-725cc06464abda7a657780f12feaefb7f10333c6.tar.gz
rust-725cc06464abda7a657780f12feaefb7f10333c6.zip
Auto merge of #22011 - fhahn:separate-parse-fail-tests, r=nikomatsakis
This PR moves all `compile-fail` tests that fail at the parsing stage to a `parse-fail` directory, in order to use the tests in the `parse-fail` directory to test if the new LALR parser rejects the same files as the Rust parser. I also adjusted the `testparser.py` script to handle the tests in `parse-fail` differently.

However during working on this, I discovered, that Rust's parser sometimes fails during parsing, but does not return a nonzero return code, e.g. compiling `/test/compile-fail/doc-before-semi.rs` with `-Z parse-only` prints an error message, but returns status code 0. Compiling the same file without `-Z parse-only`, the same error message is displayed, but error code 101 returned. I'll look into that over the next week.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions