Update pass modes for ui tests (#380)

This commit is contained in:
Yuki Okushi 2019-07-04 20:39:45 +09:00 committed by Vadim Petrochenkov
parent dd1898f265
commit 6cd76867e7
1 changed files with 5 additions and 3 deletions

View File

@ -171,8 +171,8 @@ source.
argument is the first version to ignore. If no second argument is argument is the first version to ignore. If no second argument is
given, all subsequent versions are ignored; otherwise, the second given, all subsequent versions are ignored; otherwise, the second
argument is the last version to ignore. argument is the last version to ignore.
* `compile-pass` for UI tests, indicates that the test is * `build-pass` for UI tests, indicates that the test is supposed to
supposed to compile, as opposed to the default where the test is successfully compile and link, as opposed to the default where the test is
supposed to error out. supposed to error out.
* `compile-flags` passes extra command-line args to the compiler, * `compile-flags` passes extra command-line args to the compiler,
e.g. `compile-flags -g` which forces debuginfo to be enabled. e.g. `compile-flags -g` which forces debuginfo to be enabled.
@ -279,7 +279,9 @@ can also make UI tests where compilation is expected to succeed, and
you can even run the resulting program. Just add one of the following you can even run the resulting program. Just add one of the following
[header commands](#header_commands): [header commands](#header_commands):
- `// compile-pass` compilation should succeed but do - `// check-pass` - compilation should succeed but skip codegen
(which is expensive and isn't supposed to fail in most cases)
- `// build-pass` compilation and linking should succeed but do
not run the resulting binary not run the resulting binary
- `// run-pass` compilation should succeed and we should run the - `// run-pass` compilation should succeed and we should run the
resulting binary resulting binary