| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
1. Added missing substitutions to the documentation in docs/TestingGuide.rst
2. Modified docs/CommandGuide/lit.rst to only document the "base" set of substitutions and to refer the reader to docs/TestingGuide.rst for more detailed info on substitutions.
Patch by bd1976llvm
Differential Revision: https://reviews.llvm.org/D29281
llvm-svn: 294586
|
|
|
|
|
|
|
|
| |
and UNSUPPORTED"
This reverts the revert in r292942.
llvm-svn: 293007
|
|
|
|
|
|
|
|
|
|
|
| |
and UNSUPPORTED"
After r292904 llvm-lit fails to emit the test results in the XML format for
Apple's internal buildbots.
rdar://30164800
llvm-svn: 292942
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A `lit` condition line is now a comma-separated list of boolean expressions.
Comma-separated expressions act as if each expression were on its own
condition line:
For REQUIRES, if every expression is true then the test will run.
For UNSUPPORTED, if every expression is false then the test will run.
For XFAIL, if every expression is false then the test is expected to succeed.
As a special case "XFAIL: *" expects the test to fail.
Examples:
# Test is expected fail on 64-bit Apple simulators and pass everywhere else
XFAIL: x86_64 && apple && !macosx
# Test is unsupported on Windows and on non-Ubuntu Linux
# and supported everywhere else
UNSUPPORTED: linux && !ubuntu, system-windows
Syntax:
* '&&', '||', '!', '(', ')'. 'true' is true. 'false' is false.
* Each test feature is a true identifier.
* Substrings of the target triple are true identifiers for UNSUPPORTED
and XFAIL, but not for REQUIRES. (This matches the current behavior.)
* All other identifiers are false.
* Identifiers are [-+=._a-zA-Z0-9]+
Differential Revision: https://reviews.llvm.org/D18185
llvm-svn: 292904
|
|
|
|
|
|
| |
This change needs to be better-coordinated with libc++.
llvm-svn: 292900
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A `lit` condition line is now a comma-separated list of boolean expressions.
Comma-separated expressions act as if each expression were on its own
condition line:
For REQUIRES, if every expression is true then the test will run.
For UNSUPPORTED, if every expression is false then the test will run.
For XFAIL, if every expression is false then the test is expected to succeed.
As a special case "XFAIL: *" expects the test to fail.
Examples:
# Test is expected fail on 64-bit Apple simulators and pass everywhere else
XFAIL: x86_64 && apple && !macosx
# Test is unsupported on Windows and on non-Ubuntu Linux
# and supported everywhere else
UNSUPPORTED: linux && !ubuntu, system-windows
Syntax:
* '&&', '||', '!', '(', ')'. 'true' is true. 'false' is false.
* Each test feature is a true identifier.
* Substrings of the target triple are true identifiers for UNSUPPORTED
and XFAIL, but not for REQUIRES. (This matches the current behavior.)
* All other identifiers are false.
* Identifiers are [-+=._a-zA-Z0-9]+
Differential Revision: https://reviews.llvm.org/D18185
llvm-svn: 292896
|
|
|
|
| |
llvm-svn: 292014
|
|
|
|
|
|
|
|
|
|
| |
Reviewers: mehdi_amini
Subscribers: llvm-commits
Differential Revision: http://reviews.llvm.org/D22245
llvm-svn: 275214
|
|
|
|
|
|
|
|
|
|
| |
Reviewers: alexfh, wolfgangp, rengolin
Subscribers: llvm-commits
Differential Revision: http://reviews.llvm.org/D22172
llvm-svn: 274949
|
|
|
|
|
|
| |
Patch by Diana Picus.
llvm-svn: 269566
|
|
|
|
|
|
| |
I broke the documentation builds when I deleted the MakefileGuide as part of the autoconf removal. At some point I'll need to do a more in-depth pass updating the documentation to remove references to the old build system.
llvm-svn: 258873
|
|
|
|
|
|
|
|
| |
This was considered a good practice but it was not documented. Now it is.
Differential Revision: http://reviews.llvm.org/D14733
llvm-svn: 253281
|
|
|
|
| |
llvm-svn: 236462
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were already requiring 2.5, which meant that people on old linux distros
had to upgrade anyway.
Requiring python 2.6 will make supporting 3.X easier as we can use the 3.X
exception syntax.
According to the discussion on llvmdev, there is not much value is requiring
just 2.6, we may as well just require 2.7.
llvm-svn: 224129
|
|
|
|
| |
llvm-svn: 221406
|
|
|
|
|
|
| |
We can just split targets_to_build in one place and make it immutable.
llvm-svn: 210496
|
|
|
|
| |
llvm-svn: 201464
|
|
|
|
| |
llvm-svn: 198771
|
|
|
|
|
|
| |
PR17608
llvm-svn: 193491
|
|
|
|
| |
llvm-svn: 188097
|
|
|
|
| |
llvm-svn: 185581
|
|
|
|
| |
llvm-svn: 177737
|
|
|
|
|
|
| |
Lit does support redirects in the 2>&1 style.
llvm-svn: 177403
|
|
|
|
|
|
|
|
| |
grep is now only mentioned once in a sentence that explicitly says it's
deprecated. For FileCheck, there's no reason to repeat part of the
documentation that exists in CommandGuide/FileCheck.
llvm-svn: 172835
|
|
|
|
|
|
|
| |
against the developer policy to include this sort of thing as SVN blame
already captures this in a far more fine-grained way.
llvm-svn: 172109
|
|
|
|
|
|
| |
fixed in r171243.
llvm-svn: 171258
|
|
|
|
|
|
| |
of grep in favor of FileCheck, and other cleanups.
llvm-svn: 169269
|
|
|
|
|
|
| |
think it adds much and keeping it up-to-date is (obviously) a chore.
llvm-svn: 169263
|
|
|
|
|
|
| |
This document is a long-time pet peeve :-) More fixes to come.
llvm-svn: 169115
|
|
|
|
| |
llvm-svn: 168288
|
|
|
|
| |
llvm-svn: 168286
|
|
|
|
| |
llvm-svn: 167998
|
|
|
|
|
|
| |
Some small related fixups to TestingGuide too.
llvm-svn: 167996
|
|
llvm-svn: 167979
|