about summary refs log tree commit diff
path: root/src/test/incremental/thinlto
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2018-04-11 14:37:39 +0000
committerbors <bors@rust-lang.org>2018-04-11 14:37:39 +0000
commit32428808b4c05c938c36ad6bd65bfbd658eb624f (patch)
tree95b41f3d17f7c7f4ff82e6d7a8b5a27e4130ae6a /src/test/incremental/thinlto
parentca26ef321c44358404ef788d315c4557eb015fb2 (diff)
parent746d63a203174f6c91396230b86f6b4fbda507c4 (diff)
downloadrust-32428808b4c05c938c36ad6bd65bfbd658eb624f.tar.gz
rust-32428808b4c05c938c36ad6bd65bfbd658eb624f.zip
Auto merge of #49861 - pnkfelix:compare-mode-nll-followup-2, r=nikomatsakis
Blindly checkpoint status of NLL mode ui tests

This takes the next (and potentially final?) step with #48879.

Namely, this PR got things to the point where I can successfully run `compiletest` on `src/test/ui` with `--compile-mode=nll`.

Here are the main pieces of it:

 1. To figure out how to even run `compiletest` normally on the ui directory, I ran `x.py test -vv`, and then looked for the `compiletest` invocation that mentioned `src/test/ui`.
 2. I took the aforementioned `compiletest` invocation and used it, adding `--compile-mode=nll` to the end. It had 170 failing cases.
 3. Due to #49855, I had to edit some of the tests so that they fail even under NLL, via `#[rustc_error]`. That's the first commit. (Then goto 2 to double-check no such tests remain.)
 4. I took the generated `build/target/test/foo.stderr` file for every case that failed, and blindly copied it to `src/test/foo.nll.stderr`. That's the second commit.
 5. Goto 2 until there were no failing cases.
 6. Remove any stamp files, and re-run `x.py test` to make sure that the edits and new `.nll.stderr` files haven't broken the pre-existing test suite.
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions