| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This patch is necessary because individual test cases are not required
to have unique names. Therefore, test cases must now
be specified explicitly in the form <TestCase>.<TestMethod>.
Because it works by regex matching, passing just <TestCase> will
still disable an entire file.
This also allows for multiple exclusion files to be specified.
Reviewers: zturner, labath, jingham, tfiala
Subscribers: lldb-commits, sas
Differential Revision: https://reviews.llvm.org/D24988
llvm-svn: 283238
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
The current implementation of the test suite allows the user to run
a certain subset of tests using '-p', but does not allow the inverse,
where a user wants to run all but some number of known failing tests.
Implement this functionality.
Reviewers: labath, zturner, tfiala
Subscribers: jingham, sas, lldb-commits
Differential Revision: https://reviews.llvm.org/D24629
llvm-svn: 282298
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** to conform to clang-format’s LLVM style. This kind of mass change has
*** two obvious implications:
Firstly, merging this particular commit into a downstream fork may be a huge
effort. Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit. The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):
find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;
The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.
Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit. There are alternatives available that will attempt
to look through this change and find the appropriate prior commit. YMMV.
llvm-svn: 280751
|
|
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D20306
llvm-svn: 269793
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use of --rerun-all-issues will enable any test method failure, not just
test methods marked with the flakey decorator, to rerun.
Currently this does not change the flakey logic's immediate rerun
attempt. I want to make sure this doesn't cause any significant issues
before changing that part.
The rerun reporting is only known to work properly with the
default (new) BasicResultsFormatter reporting. Once we work out
any issues, I'll go back and make sure the curses output handles
it properly as well.
llvm-svn: 255543
|
|
|
|
|
|
|
| |
Reviewed By: Tamas Berghammer, Pavel Labath
Differential Revision: http://reviews.llvm.org/D15428
llvm-svn: 255525
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also adds full path info for exceptional exits and timeouts when
no test method is currently running.
Adds --rerun-all-issues command line arg. If specified, all
test issues are eligible for rerun. If not specified, only tests
marked flakey are eligible for rerun.
The actual rerunning will occur in an upcoming change. This
change just handles tha accounting of what should be rerun.
llvm-svn: 255438
|
|
|
|
| |
llvm-svn: 255361
|
|
|
|
| |
llvm-svn: 255360
|
|
|
|
|
|
|
| |
And, turns off verbose mode by default. This must have been switched
on as the default when somebody was testing.
llvm-svn: 255310
|
|
|
|
| |
llvm-svn: 255280
|
|
|
|
| |
llvm-svn: 255279
|
|
|
|
| |
llvm-svn: 255277
|
|
|
|
| |
llvm-svn: 255276
|
|
|
|
|
|
|
|
| |
This was an option to display a graphical progress bar. Nobody
is using this, and it doesn't work correctly anyway with the new
result formatter.
llvm-svn: 255153
|
|
|
|
|
|
|
| |
This removes the option to not print some one time version and
diagnostic information when running the test suite.
llvm-svn: 255152
|
|
|
|
|
|
|
| |
This is part of a larger effort to remove unused command line
options from dotest.py.
llvm-svn: 255151
|
|
|
|
|
|
|
|
| |
This removes the failfast command line option as part of an effort
to simplify dotest and remove unused command line options. You can
still Ctrl+C any time you want to exit early.
llvm-svn: 255150
|
|
|
|
|
|
| |
This is part of an effort to remove unused command line options.
llvm-svn: 255143
|
|
|
|
|
|
|
| |
This is part of an effort to clean up dotest command line options
that are no longer used.
llvm-svn: 255142
|
|
|
|
|
|
|
|
|
|
| |
This seems to be a legacy relic from days gone by where the
remote test suite runner operated completely differently than it
does today. git blames and comments traced this functionality
back to about 2012, and nobody seems to know anything about it
now.
llvm-svn: 255060
|
|
|
|
|
|
|
|
| |
This removes the option to exclude a single directory. This is
part of an effort to remove unused options and cleanup the interface
to the test suite.
llvm-svn: 255048
|
|
|
|
|
|
|
|
| |
This removes the non-exclusive filterspec option as part of an
effort to remove unused / deprecated command line options from
dotest.
llvm-svn: 255041
|
|
|
|
|
|
|
| |
This removes the blacklist option as part of an effort to remove
unused / unmaintained command line options from the test suite.
llvm-svn: 255040
|
|
|
|
| |
llvm-svn: 255037
|
|
|
|
|
|
|
| |
This removes the option to dump Python sys.path variable as part
of an effort to remove unused options.
llvm-svn: 255035
|
|
|
|
| |
llvm-svn: 255013
|
|
|
|
| |
llvm-svn: 254983
|
|
This moves all the global variables into a separate module called
`configuration`. This has a number of advantages:
1. Configuration data is centrally maintained so it's easy to get
a high level overview of what configuration data the test suite
makes use of.
2. The method of sharing configuration data among different parts
of the test suite becomes standardized. Previously we would
put some things into the `lldb` module, some things into the
`lldbtest_config` module, and some things would not get shared.
Now everything is shared through one module and is available to
the entire test suite.
3. It opens the door to moving some of the initialization code into
the `configuration` module, simplifying the implementation of
`dotest.py`.
There are a few stragglers that didn't get converted over to using
the `configuration` module in this patch, because it would have grown
the size of the patch unnecessarily. This includes everything
currently in the `lldbtest_config` module, as well as the
`lldb.remote_platform` variable. We can address these in the future.
llvm-svn: 254982
|