2015-10-29 01:43:26 +08:00
|
|
|
"""
|
|
|
|
A simple testing framework for lldb using python's unit testing framework.
|
|
|
|
|
|
|
|
Tests for lldb are written as python scripts which take advantage of the script
|
|
|
|
bridging provided by LLDB.framework to interact with lldb core.
|
|
|
|
|
|
|
|
A specific naming pattern is followed by the .py script to be recognized as
|
|
|
|
a module which implements a test scenario, namely, Test*.py.
|
|
|
|
|
|
|
|
To specify the directories where "Test*.py" python test scripts are located,
|
|
|
|
you need to pass in a list of directory names. By default, the current
|
|
|
|
working directory is searched if nothing is specified on the command line.
|
|
|
|
|
|
|
|
Type:
|
|
|
|
|
|
|
|
./dotest.py -h
|
|
|
|
|
|
|
|
for available options.
|
|
|
|
"""
|
|
|
|
|
Python 3 - Turn on absolute imports, and fix existing imports.
Absolute imports were introduced in Python 2.5 as a feature
(e.g. from __future__ import absolute_import), and made default
in Python 3.
When absolute imports are enabled, the import system changes in
a couple of ways:
1) The `import foo` syntax will *only* search sys.path. If `foo`
isn't in sys.path, it won't be found. Period. Without absolute
imports, the import system will also search the same directory
that the importing file resides in, so that you can easily
import from the same folder.
2) From inside a package, you can use a dot syntax to refer to higher
levels of the current package. For example, if you are in the
package lldbsuite.test.utility, then ..foo refers to
lldbsuite.test.foo. You can use this notation with the
`from X import Y` syntax to write intra-package references. For
example, using the previous locationa s a starting point, writing
`from ..support import seven` would import lldbsuite.support.seven
Since this is now the default behavior in Python 3, this means that
importing from the same directory with `import foo` *no longer works*.
As a result, the only way to have portable code is to force absolute
imports for all versions of Python.
See PEP 0328 [https://www.python.org/dev/peps/pep-0328/] for more
information about absolute and relative imports.
Differential Revision: http://reviews.llvm.org/D14342
Reviewed By: Todd Fiala
llvm-svn: 252191
2015-11-06 03:22:28 +08:00
|
|
|
from __future__ import absolute_import
|
2015-10-29 01:43:26 +08:00
|
|
|
from __future__ import print_function
|
2015-11-03 03:38:58 +08:00
|
|
|
|
Python 3 - Turn on absolute imports, and fix existing imports.
Absolute imports were introduced in Python 2.5 as a feature
(e.g. from __future__ import absolute_import), and made default
in Python 3.
When absolute imports are enabled, the import system changes in
a couple of ways:
1) The `import foo` syntax will *only* search sys.path. If `foo`
isn't in sys.path, it won't be found. Period. Without absolute
imports, the import system will also search the same directory
that the importing file resides in, so that you can easily
import from the same folder.
2) From inside a package, you can use a dot syntax to refer to higher
levels of the current package. For example, if you are in the
package lldbsuite.test.utility, then ..foo refers to
lldbsuite.test.foo. You can use this notation with the
`from X import Y` syntax to write intra-package references. For
example, using the previous locationa s a starting point, writing
`from ..support import seven` would import lldbsuite.support.seven
Since this is now the default behavior in Python 3, this means that
importing from the same directory with `import foo` *no longer works*.
As a result, the only way to have portable code is to force absolute
imports for all versions of Python.
See PEP 0328 [https://www.python.org/dev/peps/pep-0328/] for more
information about absolute and relative imports.
Differential Revision: http://reviews.llvm.org/D14342
Reviewed By: Todd Fiala
llvm-svn: 252191
2015-11-06 03:22:28 +08:00
|
|
|
# System modules
|
2015-10-29 01:43:26 +08:00
|
|
|
import atexit
|
2019-08-29 04:54:17 +08:00
|
|
|
import datetime
|
2015-10-29 01:43:26 +08:00
|
|
|
import errno
|
2017-03-18 02:10:58 +08:00
|
|
|
import logging
|
2019-08-29 04:54:17 +08:00
|
|
|
import os
|
2015-10-29 01:43:26 +08:00
|
|
|
import platform
|
2016-09-24 05:32:47 +08:00
|
|
|
import re
|
2015-10-29 01:43:26 +08:00
|
|
|
import signal
|
|
|
|
import subprocess
|
|
|
|
import sys
|
2019-12-11 08:48:33 +08:00
|
|
|
import tempfile
|
2015-10-29 01:43:26 +08:00
|
|
|
|
Python 3 - Turn on absolute imports, and fix existing imports.
Absolute imports were introduced in Python 2.5 as a feature
(e.g. from __future__ import absolute_import), and made default
in Python 3.
When absolute imports are enabled, the import system changes in
a couple of ways:
1) The `import foo` syntax will *only* search sys.path. If `foo`
isn't in sys.path, it won't be found. Period. Without absolute
imports, the import system will also search the same directory
that the importing file resides in, so that you can easily
import from the same folder.
2) From inside a package, you can use a dot syntax to refer to higher
levels of the current package. For example, if you are in the
package lldbsuite.test.utility, then ..foo refers to
lldbsuite.test.foo. You can use this notation with the
`from X import Y` syntax to write intra-package references. For
example, using the previous locationa s a starting point, writing
`from ..support import seven` would import lldbsuite.support.seven
Since this is now the default behavior in Python 3, this means that
importing from the same directory with `import foo` *no longer works*.
As a result, the only way to have portable code is to force absolute
imports for all versions of Python.
See PEP 0328 [https://www.python.org/dev/peps/pep-0328/] for more
information about absolute and relative imports.
Differential Revision: http://reviews.llvm.org/D14342
Reviewed By: Todd Fiala
llvm-svn: 252191
2015-11-06 03:22:28 +08:00
|
|
|
# Third-party modules
|
2015-10-29 01:43:26 +08:00
|
|
|
import six
|
Python 3 - Turn on absolute imports, and fix existing imports.
Absolute imports were introduced in Python 2.5 as a feature
(e.g. from __future__ import absolute_import), and made default
in Python 3.
When absolute imports are enabled, the import system changes in
a couple of ways:
1) The `import foo` syntax will *only* search sys.path. If `foo`
isn't in sys.path, it won't be found. Period. Without absolute
imports, the import system will also search the same directory
that the importing file resides in, so that you can easily
import from the same folder.
2) From inside a package, you can use a dot syntax to refer to higher
levels of the current package. For example, if you are in the
package lldbsuite.test.utility, then ..foo refers to
lldbsuite.test.foo. You can use this notation with the
`from X import Y` syntax to write intra-package references. For
example, using the previous locationa s a starting point, writing
`from ..support import seven` would import lldbsuite.support.seven
Since this is now the default behavior in Python 3, this means that
importing from the same directory with `import foo` *no longer works*.
As a result, the only way to have portable code is to force absolute
imports for all versions of Python.
See PEP 0328 [https://www.python.org/dev/peps/pep-0328/] for more
information about absolute and relative imports.
Differential Revision: http://reviews.llvm.org/D14342
Reviewed By: Todd Fiala
llvm-svn: 252191
2015-11-06 03:22:28 +08:00
|
|
|
import unittest2
|
|
|
|
|
|
|
|
# LLDB Modules
|
|
|
|
import lldbsuite
|
2015-12-08 09:15:30 +08:00
|
|
|
from . import configuration
|
Python 3 - Turn on absolute imports, and fix existing imports.
Absolute imports were introduced in Python 2.5 as a feature
(e.g. from __future__ import absolute_import), and made default
in Python 3.
When absolute imports are enabled, the import system changes in
a couple of ways:
1) The `import foo` syntax will *only* search sys.path. If `foo`
isn't in sys.path, it won't be found. Period. Without absolute
imports, the import system will also search the same directory
that the importing file resides in, so that you can easily
import from the same folder.
2) From inside a package, you can use a dot syntax to refer to higher
levels of the current package. For example, if you are in the
package lldbsuite.test.utility, then ..foo refers to
lldbsuite.test.foo. You can use this notation with the
`from X import Y` syntax to write intra-package references. For
example, using the previous locationa s a starting point, writing
`from ..support import seven` would import lldbsuite.support.seven
Since this is now the default behavior in Python 3, this means that
importing from the same directory with `import foo` *no longer works*.
As a result, the only way to have portable code is to force absolute
imports for all versions of Python.
See PEP 0328 [https://www.python.org/dev/peps/pep-0328/] for more
information about absolute and relative imports.
Differential Revision: http://reviews.llvm.org/D14342
Reviewed By: Todd Fiala
llvm-svn: 252191
2015-11-06 03:22:28 +08:00
|
|
|
from . import dotest_args
|
|
|
|
from . import lldbtest_config
|
|
|
|
from . import test_categories
|
2015-12-08 09:15:44 +08:00
|
|
|
from . import test_result
|
Python 3 - Turn on absolute imports, and fix existing imports.
Absolute imports were introduced in Python 2.5 as a feature
(e.g. from __future__ import absolute_import), and made default
in Python 3.
When absolute imports are enabled, the import system changes in
a couple of ways:
1) The `import foo` syntax will *only* search sys.path. If `foo`
isn't in sys.path, it won't be found. Period. Without absolute
imports, the import system will also search the same directory
that the importing file resides in, so that you can easily
import from the same folder.
2) From inside a package, you can use a dot syntax to refer to higher
levels of the current package. For example, if you are in the
package lldbsuite.test.utility, then ..foo refers to
lldbsuite.test.foo. You can use this notation with the
`from X import Y` syntax to write intra-package references. For
example, using the previous locationa s a starting point, writing
`from ..support import seven` would import lldbsuite.support.seven
Since this is now the default behavior in Python 3, this means that
importing from the same directory with `import foo` *no longer works*.
As a result, the only way to have portable code is to force absolute
imports for all versions of Python.
See PEP 0328 [https://www.python.org/dev/peps/pep-0328/] for more
information about absolute and relative imports.
Differential Revision: http://reviews.llvm.org/D14342
Reviewed By: Todd Fiala
llvm-svn: 252191
2015-11-06 03:22:28 +08:00
|
|
|
from ..support import seven
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2016-09-07 04:57:50 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def is_exe(fpath):
|
2017-10-25 00:07:50 +08:00
|
|
|
"""Returns true if fpath is an executable."""
|
2018-01-27 05:46:10 +08:00
|
|
|
if fpath == None:
|
2019-08-30 02:37:05 +08:00
|
|
|
return False
|
2020-10-08 23:46:04 +08:00
|
|
|
if sys.platform == 'win32':
|
|
|
|
if not fpath.endswith(".exe"):
|
|
|
|
fpath += ".exe"
|
2015-10-29 01:43:26 +08:00
|
|
|
return os.path.isfile(fpath) and os.access(fpath, os.X_OK)
|
|
|
|
|
2016-09-07 04:57:50 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def which(program):
|
|
|
|
"""Returns the full path to a program; None otherwise."""
|
2019-07-26 09:58:18 +08:00
|
|
|
fpath, _ = os.path.split(program)
|
2015-10-29 01:43:26 +08:00
|
|
|
if fpath:
|
|
|
|
if is_exe(program):
|
|
|
|
return program
|
|
|
|
else:
|
|
|
|
for path in os.environ["PATH"].split(os.pathsep):
|
|
|
|
exe_file = os.path.join(path, program)
|
|
|
|
if is_exe(exe_file):
|
|
|
|
return exe_file
|
|
|
|
return None
|
|
|
|
|
2016-09-07 04:57:50 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def usage(parser):
|
|
|
|
parser.print_help()
|
2015-12-08 09:15:30 +08:00
|
|
|
if configuration.verbose > 0:
|
2015-10-29 01:43:26 +08:00
|
|
|
print("""
|
|
|
|
Examples:
|
|
|
|
|
|
|
|
This is an example of using the -f option to pinpoint to a specific test class
|
|
|
|
and test method to be run:
|
|
|
|
|
|
|
|
$ ./dotest.py -f ClassTypesTestCase.test_with_dsym_and_run_command
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
Collected 1 test
|
|
|
|
|
|
|
|
test_with_dsym_and_run_command (TestClassTypes.ClassTypesTestCase)
|
|
|
|
Test 'frame variable this' when stopped on a class constructor. ... ok
|
|
|
|
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
Ran 1 test in 1.396s
|
|
|
|
|
|
|
|
OK
|
|
|
|
|
|
|
|
And this is an example of using the -p option to run a single file (the filename
|
|
|
|
matches the pattern 'ObjC' and it happens to be 'TestObjCMethods.py'):
|
|
|
|
|
|
|
|
$ ./dotest.py -v -p ObjC
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
Collected 4 tests
|
|
|
|
|
|
|
|
test_break_with_dsym (TestObjCMethods.FoundationTestCase)
|
|
|
|
Test setting objc breakpoints using '_regexp-break' and 'breakpoint set'. ... ok
|
|
|
|
test_break_with_dwarf (TestObjCMethods.FoundationTestCase)
|
|
|
|
Test setting objc breakpoints using '_regexp-break' and 'breakpoint set'. ... ok
|
|
|
|
test_data_type_and_expr_with_dsym (TestObjCMethods.FoundationTestCase)
|
|
|
|
Lookup objective-c data types and evaluate expressions. ... ok
|
|
|
|
test_data_type_and_expr_with_dwarf (TestObjCMethods.FoundationTestCase)
|
|
|
|
Lookup objective-c data types and evaluate expressions. ... ok
|
|
|
|
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
Ran 4 tests in 16.661s
|
|
|
|
|
|
|
|
OK
|
|
|
|
|
|
|
|
Running of this script also sets up the LLDB_TEST environment variable so that
|
|
|
|
individual test cases can locate their supporting files correctly. The script
|
|
|
|
tries to set up Python's search paths for modules by looking at the build tree
|
|
|
|
relative to this script. See also the '-i' option in the following example.
|
|
|
|
|
|
|
|
Finally, this is an example of using the lldb.py module distributed/installed by
|
|
|
|
Xcode4 to run against the tests under the 'forward' directory, and with the '-w'
|
|
|
|
option to add some delay between two tests. It uses ARCH=x86_64 to specify that
|
|
|
|
as the architecture and CC=clang to specify the compiler used for the test run:
|
|
|
|
|
|
|
|
$ PYTHONPATH=/Xcode4/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Python ARCH=x86_64 CC=clang ./dotest.py -v -w -i forward
|
|
|
|
|
|
|
|
Session logs for test failures/errors will go into directory '2010-11-11-13_56_16'
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
Collected 2 tests
|
|
|
|
|
|
|
|
test_with_dsym_and_run_command (TestForwardDeclaration.ForwardDeclarationTestCase)
|
|
|
|
Display *bar_ptr when stopped on a function with forward declaration of struct bar. ... ok
|
|
|
|
test_with_dwarf_and_run_command (TestForwardDeclaration.ForwardDeclarationTestCase)
|
|
|
|
Display *bar_ptr when stopped on a function with forward declaration of struct bar. ... ok
|
|
|
|
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
Ran 2 tests in 5.659s
|
|
|
|
|
|
|
|
OK
|
|
|
|
|
|
|
|
The 'Session ...' verbiage is recently introduced (see also the '-s' option) to
|
|
|
|
notify the directory containing the session logs for test failures or errors.
|
|
|
|
In case there is any test failure/error, a similar message is appended at the
|
|
|
|
end of the stderr output for your convenience.
|
|
|
|
|
|
|
|
ENABLING LOGS FROM TESTS
|
|
|
|
|
|
|
|
Option 1:
|
|
|
|
|
|
|
|
Writing logs into different files per test case::
|
|
|
|
|
|
|
|
$ ./dotest.py --channel "lldb all"
|
|
|
|
|
|
|
|
$ ./dotest.py --channel "lldb all" --channel "gdb-remote packets"
|
|
|
|
|
|
|
|
These log files are written to:
|
|
|
|
|
|
|
|
<session-dir>/<test-id>-host.log (logs from lldb host process)
|
|
|
|
<session-dir>/<test-id>-server.log (logs from debugserver/lldb-server)
|
|
|
|
<session-dir>/<test-id>-<test-result>.log (console logs)
|
|
|
|
|
|
|
|
By default, logs from successful runs are deleted. Use the --log-success flag
|
|
|
|
to create reference logs for debugging.
|
|
|
|
|
|
|
|
$ ./dotest.py --log-success
|
|
|
|
|
|
|
|
""")
|
|
|
|
sys.exit(0)
|
|
|
|
|
2016-09-07 04:57:50 +08:00
|
|
|
|
2016-09-24 05:32:47 +08:00
|
|
|
def parseExclusion(exclusion_file):
|
|
|
|
"""Parse an exclusion file, of the following format, where
|
|
|
|
'skip files', 'skip methods', 'xfail files', and 'xfail methods'
|
|
|
|
are the possible list heading values:
|
|
|
|
|
|
|
|
skip files
|
|
|
|
<file name>
|
|
|
|
<file name>
|
|
|
|
|
|
|
|
xfail methods
|
|
|
|
<method name>
|
|
|
|
"""
|
|
|
|
excl_type = None
|
|
|
|
|
|
|
|
with open(exclusion_file) as f:
|
|
|
|
for line in f:
|
2016-10-05 02:48:00 +08:00
|
|
|
line = line.strip()
|
2016-09-24 05:32:47 +08:00
|
|
|
if not excl_type:
|
2016-10-05 02:48:00 +08:00
|
|
|
excl_type = line
|
2016-09-24 05:32:47 +08:00
|
|
|
continue
|
|
|
|
|
|
|
|
if not line:
|
|
|
|
excl_type = None
|
2016-10-05 02:48:00 +08:00
|
|
|
elif excl_type == 'skip':
|
|
|
|
if not configuration.skip_tests:
|
|
|
|
configuration.skip_tests = []
|
|
|
|
configuration.skip_tests.append(line)
|
|
|
|
elif excl_type == 'xfail':
|
|
|
|
if not configuration.xfail_tests:
|
|
|
|
configuration.xfail_tests = []
|
|
|
|
configuration.xfail_tests.append(line)
|
2016-09-24 05:32:47 +08:00
|
|
|
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def parseOptionsAndInitTestdirs():
|
|
|
|
"""Initialize the list of directories containing our unittest scripts.
|
|
|
|
|
|
|
|
'-h/--help as the first option prints out usage info and exit the program.
|
|
|
|
"""
|
|
|
|
|
|
|
|
do_help = False
|
|
|
|
|
|
|
|
platform_system = platform.system()
|
|
|
|
platform_machine = platform.machine()
|
|
|
|
|
2019-08-27 00:08:53 +08:00
|
|
|
try:
|
|
|
|
parser = dotest_args.create_parser()
|
2019-08-29 07:54:23 +08:00
|
|
|
args = parser.parse_args()
|
2019-08-27 00:08:53 +08:00
|
|
|
except:
|
|
|
|
raise
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
if args.unset_env_varnames:
|
|
|
|
for env_var in args.unset_env_varnames:
|
|
|
|
if env_var in os.environ:
|
|
|
|
# From Python Doc: When unsetenv() is supported, deletion of items in os.environ
|
|
|
|
# is automatically translated into a corresponding call to
|
|
|
|
# unsetenv().
|
|
|
|
del os.environ[env_var]
|
|
|
|
# os.unsetenv(env_var)
|
|
|
|
|
|
|
|
if args.set_env_vars:
|
|
|
|
for env_var in args.set_env_vars:
|
|
|
|
parts = env_var.split('=', 1)
|
|
|
|
if len(parts) == 1:
|
|
|
|
os.environ[parts[0]] = ""
|
|
|
|
else:
|
|
|
|
os.environ[parts[0]] = parts[1]
|
|
|
|
|
2019-06-27 00:12:08 +08:00
|
|
|
if args.set_inferior_env_vars:
|
|
|
|
lldbtest_config.inferior_env = ' '.join(args.set_inferior_env_vars)
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
if args.h:
|
|
|
|
do_help = True
|
|
|
|
|
2017-03-15 16:51:59 +08:00
|
|
|
if args.compiler:
|
2020-08-04 08:33:37 +08:00
|
|
|
configuration.compiler = os.path.abspath(args.compiler)
|
2017-03-18 05:00:35 +08:00
|
|
|
if not is_exe(configuration.compiler):
|
|
|
|
configuration.compiler = which(args.compiler)
|
2017-03-18 02:10:58 +08:00
|
|
|
if not is_exe(configuration.compiler):
|
|
|
|
logging.error(
|
|
|
|
'%s is not a valid compiler executable; aborting...',
|
|
|
|
args.compiler)
|
|
|
|
sys.exit(-1)
|
2015-10-29 01:43:26 +08:00
|
|
|
else:
|
|
|
|
# Use a compiler appropriate appropriate for the Apple SDK if one was
|
|
|
|
# specified
|
|
|
|
if platform_system == 'Darwin' and args.apple_sdk:
|
2017-03-15 16:51:59 +08:00
|
|
|
configuration.compiler = seven.get_command_output(
|
|
|
|
'xcrun -sdk "%s" -find clang 2> /dev/null' %
|
|
|
|
(args.apple_sdk))
|
2015-10-29 01:43:26 +08:00
|
|
|
else:
|
|
|
|
# 'clang' on ubuntu 14.04 is 3.4 so we try clang-3.5 first
|
|
|
|
candidateCompilers = ['clang-3.5', 'clang', 'gcc']
|
|
|
|
for candidate in candidateCompilers:
|
|
|
|
if which(candidate):
|
2017-03-15 16:51:59 +08:00
|
|
|
configuration.compiler = candidate
|
2015-10-29 01:43:26 +08:00
|
|
|
break
|
|
|
|
|
2018-04-12 17:25:32 +08:00
|
|
|
if args.dsymutil:
|
2020-06-03 07:49:03 +08:00
|
|
|
configuration.dsymutil = args.dsymutil
|
2018-04-12 17:35:17 +08:00
|
|
|
elif platform_system == 'Darwin':
|
2020-06-03 07:49:03 +08:00
|
|
|
configuration.dsymutil = seven.get_command_output(
|
2019-08-30 02:37:05 +08:00
|
|
|
'xcrun -find -toolchain default dsymutil')
|
2018-04-12 17:25:32 +08:00
|
|
|
|
2020-07-11 12:14:06 +08:00
|
|
|
|
|
|
|
# The lldb-dotest script produced by the CMake build passes in a path to a
|
|
|
|
# working FileCheck and yaml2obj binary. So does one specific Xcode
|
|
|
|
# project target. However, when invoking dotest.py directly, a valid
|
|
|
|
# --filecheck and --yaml2obj option needs to be given.
|
2018-09-19 03:31:47 +08:00
|
|
|
if args.filecheck:
|
|
|
|
configuration.filecheck = os.path.abspath(args.filecheck)
|
2018-10-13 03:29:59 +08:00
|
|
|
|
2020-07-11 12:14:06 +08:00
|
|
|
if args.yaml2obj:
|
|
|
|
configuration.yaml2obj = os.path.abspath(args.yaml2obj)
|
|
|
|
|
2018-10-13 03:29:59 +08:00
|
|
|
if not configuration.get_filecheck_path():
|
|
|
|
logging.warning('No valid FileCheck executable; some tests may fail...')
|
|
|
|
logging.warning('(Double-check the --filecheck argument to dotest.py)')
|
2018-09-19 03:31:47 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
if args.channels:
|
|
|
|
lldbtest_config.channels = args.channels
|
|
|
|
|
|
|
|
if args.log_success:
|
|
|
|
lldbtest_config.log_success = args.log_success
|
|
|
|
|
2018-03-09 03:46:39 +08:00
|
|
|
if args.out_of_tree_debugserver:
|
|
|
|
lldbtest_config.out_of_tree_debugserver = args.out_of_tree_debugserver
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
# Set SDKROOT if we are using an Apple SDK
|
|
|
|
if platform_system == 'Darwin' and args.apple_sdk:
|
2020-06-03 07:49:03 +08:00
|
|
|
configuration.sdkroot = seven.get_command_output(
|
2015-11-04 02:55:22 +08:00
|
|
|
'xcrun --sdk "%s" --show-sdk-path 2> /dev/null' %
|
|
|
|
(args.apple_sdk))
|
2020-10-13 21:07:33 +08:00
|
|
|
if not configuration.sdkroot:
|
|
|
|
logging.error(
|
|
|
|
'No SDK found with the name %s; aborting...',
|
|
|
|
args.apple_sdk)
|
|
|
|
sys.exit(-1)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2017-03-15 16:51:59 +08:00
|
|
|
if args.arch:
|
|
|
|
configuration.arch = args.arch
|
2015-10-29 01:43:26 +08:00
|
|
|
else:
|
2017-03-15 16:51:59 +08:00
|
|
|
configuration.arch = platform_machine
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2019-12-12 19:17:14 +08:00
|
|
|
if args.categories_list:
|
|
|
|
configuration.categories_list = set(
|
2015-12-08 09:15:30 +08:00
|
|
|
test_categories.validate(
|
2019-12-12 19:17:14 +08:00
|
|
|
args.categories_list, False))
|
|
|
|
configuration.use_categories = True
|
2015-10-29 01:43:26 +08:00
|
|
|
else:
|
2019-12-12 19:17:14 +08:00
|
|
|
configuration.categories_list = []
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2019-12-12 19:17:14 +08:00
|
|
|
if args.skip_categories:
|
|
|
|
configuration.skip_categories += test_categories.validate(
|
|
|
|
args.skip_categories, False)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2019-12-12 20:01:25 +08:00
|
|
|
if args.xfail_categories:
|
|
|
|
configuration.xfail_categories += test_categories.validate(
|
|
|
|
args.xfail_categories, False)
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
if args.E:
|
2019-08-21 07:56:32 +08:00
|
|
|
os.environ['CFLAGS_EXTRAS'] = args.E
|
2019-08-20 00:04:21 +08:00
|
|
|
|
|
|
|
if args.dwarf_version:
|
|
|
|
configuration.dwarf_version = args.dwarf_version
|
2019-08-21 07:56:32 +08:00
|
|
|
# We cannot modify CFLAGS_EXTRAS because they're used in test cases
|
|
|
|
# that explicitly require no debug info.
|
|
|
|
os.environ['CFLAGS'] = '-gdwarf-{}'.format(configuration.dwarf_version)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2020-01-15 04:34:13 +08:00
|
|
|
if args.settings:
|
|
|
|
for setting in args.settings:
|
|
|
|
if not len(setting) == 1 or not setting[0].count('='):
|
|
|
|
logging.error('"%s" is not a setting in the form "key=value"',
|
|
|
|
setting[0])
|
|
|
|
sys.exit(-1)
|
2020-03-13 08:47:27 +08:00
|
|
|
setting_list = setting[0].split('=', 1)
|
|
|
|
configuration.settings.append((setting_list[0], setting_list[1]))
|
2020-01-15 04:34:13 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
if args.d:
|
|
|
|
sys.stdout.write(
|
|
|
|
"Suspending the process %d to wait for debugger to attach...\n" %
|
|
|
|
os.getpid())
|
|
|
|
sys.stdout.flush()
|
|
|
|
os.kill(os.getpid(), signal.SIGSTOP)
|
|
|
|
|
|
|
|
if args.f:
|
|
|
|
if any([x.startswith('-') for x in args.f]):
|
|
|
|
usage(parser)
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.filters.extend(args.f)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
if args.framework:
|
2019-12-12 19:17:14 +08:00
|
|
|
configuration.lldb_framework_path = args.framework
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
if args.executable:
|
2017-03-18 02:10:58 +08:00
|
|
|
# lldb executable is passed explicitly
|
2016-04-26 04:36:22 +08:00
|
|
|
lldbtest_config.lldbExec = os.path.realpath(args.executable)
|
2017-03-18 05:00:35 +08:00
|
|
|
if not is_exe(lldbtest_config.lldbExec):
|
|
|
|
lldbtest_config.lldbExec = which(args.executable)
|
2017-03-18 02:10:58 +08:00
|
|
|
if not is_exe(lldbtest_config.lldbExec):
|
|
|
|
logging.error(
|
|
|
|
'%s is not a valid executable to test; aborting...',
|
|
|
|
args.executable)
|
|
|
|
sys.exit(-1)
|
|
|
|
|
2020-07-08 06:03:08 +08:00
|
|
|
if args.server and args.out_of_tree_debugserver:
|
|
|
|
logging.warning('Both --server and --out-of-tree-debugserver are set')
|
|
|
|
|
2020-07-08 06:00:08 +08:00
|
|
|
if args.server and not args.out_of_tree_debugserver:
|
2017-03-15 04:04:46 +08:00
|
|
|
os.environ['LLDB_DEBUGSERVER_PATH'] = args.server
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2016-09-24 05:32:47 +08:00
|
|
|
if args.excluded:
|
2016-10-05 02:48:00 +08:00
|
|
|
for excl_file in args.excluded:
|
|
|
|
parseExclusion(excl_file)
|
2016-09-24 05:32:47 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
if args.p:
|
|
|
|
if args.p.startswith('-'):
|
|
|
|
usage(parser)
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.regexp = args.p
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
if args.t:
|
|
|
|
os.environ['LLDB_COMMAND_TRACE'] = 'YES'
|
|
|
|
|
|
|
|
if args.v:
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.verbose = 2
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
# argparse makes sure we have a number
|
|
|
|
if args.sharp:
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.count = args.sharp
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
if sys.platform.startswith('win32'):
|
|
|
|
os.environ['LLDB_DISABLE_CRASH_DIALOG'] = str(
|
|
|
|
args.disable_crash_dialog)
|
2015-12-11 02:51:02 +08:00
|
|
|
os.environ['LLDB_LAUNCH_INFERIORS_WITHOUT_CONSOLE'] = str(True)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
if do_help:
|
|
|
|
usage(parser)
|
|
|
|
|
2020-04-14 23:41:50 +08:00
|
|
|
# Reproducer arguments
|
|
|
|
if args.capture_path and args.replay_path:
|
|
|
|
logging.error('Cannot specify both a capture and a replay path.')
|
|
|
|
sys.exit(-1)
|
|
|
|
|
|
|
|
if args.capture_path:
|
|
|
|
configuration.capture_path = args.capture_path
|
|
|
|
|
|
|
|
if args.replay_path:
|
|
|
|
configuration.replay_path = args.replay_path
|
2015-10-29 01:43:26 +08:00
|
|
|
if args.lldb_platform_name:
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.lldb_platform_name = args.lldb_platform_name
|
2015-10-29 01:43:26 +08:00
|
|
|
if args.lldb_platform_url:
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.lldb_platform_url = args.lldb_platform_url
|
2015-10-29 01:43:26 +08:00
|
|
|
if args.lldb_platform_working_dir:
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.lldb_platform_working_dir = args.lldb_platform_working_dir
|
2020-08-08 04:04:16 +08:00
|
|
|
if platform_system == 'Darwin' and args.apple_sdk:
|
2020-08-08 01:06:38 +08:00
|
|
|
configuration.apple_sdk = args.apple_sdk
|
2018-01-31 02:29:16 +08:00
|
|
|
if args.test_build_dir:
|
|
|
|
configuration.test_build_dir = args.test_build_dir
|
2019-10-11 01:27:09 +08:00
|
|
|
if args.lldb_module_cache_dir:
|
|
|
|
configuration.lldb_module_cache_dir = args.lldb_module_cache_dir
|
2019-08-30 02:37:05 +08:00
|
|
|
else:
|
2019-10-11 01:27:09 +08:00
|
|
|
configuration.lldb_module_cache_dir = os.path.join(
|
|
|
|
configuration.test_build_dir, 'module-cache-lldb')
|
|
|
|
if args.clang_module_cache_dir:
|
|
|
|
configuration.clang_module_cache_dir = args.clang_module_cache_dir
|
|
|
|
else:
|
|
|
|
configuration.clang_module_cache_dir = os.path.join(
|
|
|
|
configuration.test_build_dir, 'module-cache-clang')
|
|
|
|
|
2020-01-31 16:35:34 +08:00
|
|
|
if args.lldb_libs_dir:
|
|
|
|
configuration.lldb_libs_dir = args.lldb_libs_dir
|
|
|
|
|
2020-04-04 10:42:58 +08:00
|
|
|
if args.enabled_plugins:
|
|
|
|
configuration.enabled_plugins = args.enabled_plugins
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
# Gather all the dirs passed on the command line.
|
|
|
|
if len(args.args) > 0:
|
2019-03-21 15:19:09 +08:00
|
|
|
configuration.testdirs = [os.path.realpath(os.path.abspath(x)) for x in args.args]
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2016-10-22 06:13:55 +08:00
|
|
|
lldbtest_config.codesign_identity = args.codesign_identity
|
|
|
|
|
2020-09-17 05:26:40 +08:00
|
|
|
def registerFaulthandler():
|
|
|
|
try:
|
|
|
|
import faulthandler
|
|
|
|
except ImportError:
|
|
|
|
# faulthandler is not available until python3
|
|
|
|
return
|
|
|
|
|
|
|
|
faulthandler.enable()
|
|
|
|
# faulthandler.register is not available on Windows.
|
|
|
|
if getattr(faulthandler, 'register', None):
|
|
|
|
faulthandler.register(signal.SIGTERM, chain=True)
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def setupSysPath():
|
|
|
|
"""
|
|
|
|
Add LLDB.framework/Resources/Python to the search paths for modules.
|
|
|
|
As a side effect, we also discover the 'lldb' executable and export it here.
|
|
|
|
"""
|
|
|
|
|
|
|
|
# Get the directory containing the current script.
|
|
|
|
if "DOTEST_PROFILE" in os.environ and "DOTEST_SCRIPT_DIR" in os.environ:
|
|
|
|
scriptPath = os.environ["DOTEST_SCRIPT_DIR"]
|
|
|
|
else:
|
2020-08-04 08:33:37 +08:00
|
|
|
scriptPath = os.path.dirname(os.path.abspath(__file__))
|
2015-10-29 01:43:26 +08:00
|
|
|
if not scriptPath.endswith('test'):
|
|
|
|
print("This script expects to reside in lldb's test directory.")
|
|
|
|
sys.exit(-1)
|
|
|
|
|
2015-12-12 03:21:34 +08:00
|
|
|
os.environ["LLDB_TEST"] = scriptPath
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2018-01-31 02:29:16 +08:00
|
|
|
# Set up the root build directory.
|
|
|
|
if not configuration.test_build_dir:
|
|
|
|
raise Exception("test_build_dir is not set")
|
2020-06-03 07:49:03 +08:00
|
|
|
configuration.test_build_dir = os.path.abspath(configuration.test_build_dir)
|
2018-01-31 02:29:16 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
# Set up the LLDB_SRC environment variable, so that the tests can locate
|
|
|
|
# the LLDB source code.
|
|
|
|
os.environ["LLDB_SRC"] = lldbsuite.lldb_root
|
|
|
|
|
|
|
|
pluginPath = os.path.join(scriptPath, 'plugins')
|
2018-08-17 01:59:38 +08:00
|
|
|
toolsLLDBVSCode = os.path.join(scriptPath, 'tools', 'lldb-vscode')
|
2015-10-29 01:43:26 +08:00
|
|
|
toolsLLDBServerPath = os.path.join(scriptPath, 'tools', 'lldb-server')
|
|
|
|
|
2019-07-19 23:55:23 +08:00
|
|
|
# Insert script dir, plugin dir and lldb-server dir to the sys.path.
|
2015-10-29 01:43:26 +08:00
|
|
|
sys.path.insert(0, pluginPath)
|
2018-08-17 01:59:38 +08:00
|
|
|
# Adding test/tools/lldb-vscode to the path makes it easy to
|
|
|
|
# "import lldb_vscode_testcase" from the VSCode tests
|
|
|
|
sys.path.insert(0, toolsLLDBVSCode)
|
2015-10-29 01:43:26 +08:00
|
|
|
# Adding test/tools/lldb-server to the path makes it easy
|
|
|
|
sys.path.insert(0, toolsLLDBServerPath)
|
|
|
|
# to "import lldbgdbserverutils" from the lldb-server tests
|
|
|
|
|
|
|
|
# This is the root of the lldb git/svn checkout
|
|
|
|
# When this changes over to a package instead of a standalone script, this
|
|
|
|
# will be `lldbsuite.lldb_root`
|
|
|
|
lldbRootDirectory = lldbsuite.lldb_root
|
|
|
|
|
|
|
|
# Some of the tests can invoke the 'lldb' command directly.
|
|
|
|
# We'll try to locate the appropriate executable right here.
|
|
|
|
|
|
|
|
# The lldb executable can be set from the command line
|
|
|
|
# if it's not set, we try to find it now
|
|
|
|
# first, we try the environment
|
|
|
|
if not lldbtest_config.lldbExec:
|
|
|
|
# First, you can define an environment variable LLDB_EXEC specifying the
|
|
|
|
# full pathname of the lldb executable.
|
|
|
|
if "LLDB_EXEC" in os.environ:
|
|
|
|
lldbtest_config.lldbExec = os.environ["LLDB_EXEC"]
|
|
|
|
|
|
|
|
if not lldbtest_config.lldbExec:
|
|
|
|
# Last, check the path
|
|
|
|
lldbtest_config.lldbExec = which('lldb')
|
|
|
|
|
|
|
|
if lldbtest_config.lldbExec and not is_exe(lldbtest_config.lldbExec):
|
|
|
|
print(
|
|
|
|
"'{}' is not a path to a valid executable".format(
|
|
|
|
lldbtest_config.lldbExec))
|
|
|
|
lldbtest_config.lldbExec = None
|
|
|
|
|
|
|
|
if not lldbtest_config.lldbExec:
|
|
|
|
print("The 'lldb' executable cannot be located. Some of the tests may not be run as a result.")
|
|
|
|
sys.exit(-1)
|
|
|
|
|
2015-12-10 04:48:42 +08:00
|
|
|
os.system('%s -v' % lldbtest_config.lldbExec)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2016-10-13 04:15:46 +08:00
|
|
|
lldbDir = os.path.dirname(lldbtest_config.lldbExec)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2018-08-17 01:59:38 +08:00
|
|
|
lldbVSCodeExec = os.path.join(lldbDir, "lldb-vscode")
|
|
|
|
if is_exe(lldbVSCodeExec):
|
|
|
|
os.environ["LLDBVSCODE_EXEC"] = lldbVSCodeExec
|
|
|
|
else:
|
|
|
|
if not configuration.shouldSkipBecauseOfCategories(["lldb-vscode"]):
|
|
|
|
print(
|
|
|
|
"The 'lldb-vscode' executable cannot be located. The lldb-vscode tests can not be run as a result.")
|
2019-12-12 19:17:14 +08:00
|
|
|
configuration.skip_categories.append("lldb-vscode")
|
2018-08-17 01:59:38 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
lldbPythonDir = None # The directory that contains 'lldb/__init__.py'
|
2020-10-06 07:35:23 +08:00
|
|
|
|
|
|
|
# If our lldb supports the -P option, use it to find the python path:
|
|
|
|
lldb_dash_p_result = subprocess.check_output([lldbtest_config.lldbExec, "-P"], universal_newlines=True)
|
|
|
|
if lldb_dash_p_result:
|
|
|
|
for line in lldb_dash_p_result.splitlines():
|
|
|
|
if os.path.isdir(line) and os.path.exists(os.path.join(line, 'lldb', '__init__.py')):
|
|
|
|
lldbPythonDir = line
|
|
|
|
break
|
|
|
|
|
|
|
|
if not lldbPythonDir:
|
|
|
|
print(
|
|
|
|
"Unable to load lldb extension module. Possible reasons for this include:")
|
|
|
|
print(" 1) LLDB was built with LLDB_ENABLE_PYTHON=0")
|
|
|
|
print(
|
|
|
|
" 2) PYTHONPATH and PYTHONHOME are not set correctly. PYTHONHOME should refer to")
|
|
|
|
print(
|
|
|
|
" the version of Python that LLDB built and linked against, and PYTHONPATH")
|
|
|
|
print(
|
|
|
|
" should contain the Lib directory for the same python distro, as well as the")
|
|
|
|
print(" location of LLDB\'s site-packages folder.")
|
|
|
|
print(
|
|
|
|
" 3) A different version of Python than that which was built against is exported in")
|
|
|
|
print(" the system\'s PATH environment variable, causing conflicts.")
|
|
|
|
print(
|
|
|
|
" 4) The executable '%s' could not be found. Please check " %
|
|
|
|
lldbtest_config.lldbExec)
|
|
|
|
print(" that it exists and is executable.")
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
if lldbPythonDir:
|
|
|
|
lldbPythonDir = os.path.normpath(lldbPythonDir)
|
|
|
|
# Some of the code that uses this path assumes it hasn't resolved the Versions... link.
|
|
|
|
# If the path we've constructed looks like that, then we'll strip out
|
|
|
|
# the Versions/A part.
|
|
|
|
(before, frameWithVersion, after) = lldbPythonDir.rpartition(
|
|
|
|
"LLDB.framework/Versions/A")
|
|
|
|
if frameWithVersion != "":
|
|
|
|
lldbPythonDir = before + "LLDB.framework" + after
|
|
|
|
|
|
|
|
lldbPythonDir = os.path.abspath(lldbPythonDir)
|
|
|
|
|
2020-10-06 07:35:23 +08:00
|
|
|
if "freebsd" in sys.platform or "linux" in sys.platform:
|
|
|
|
os.environ['LLDB_LIB_DIR'] = os.path.join(lldbPythonDir, '..', '..')
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
# If tests need to find LLDB_FRAMEWORK, now they can do it
|
|
|
|
os.environ["LLDB_FRAMEWORK"] = os.path.dirname(
|
|
|
|
os.path.dirname(lldbPythonDir))
|
|
|
|
|
|
|
|
# This is to locate the lldb.py module. Insert it right after
|
|
|
|
# sys.path[0].
|
|
|
|
sys.path[1:1] = [lldbPythonDir]
|
|
|
|
|
test infra: catch bad decorators and import-time errors
Summary:
This change enhances the LLDB test infrastructure to convert
load-time exceptions in a given Python test module into errors.
Before this change, specifying a non-existent test decorator,
or otherwise having some load-time error in a python test module,
would not get flagged as an error.
With this change, typos and other load-time errors in a python
test file get converted to errors and reported by the
test runner.
This change also includes test infrastructure tests that include
covering the new work here. I'm going to wait until we have
these infrastructure tests runnable on the main platforms before
I try to work that into all the normal testing workflows.
The test infrastructure tests can be run by using the standard python module testing practice of doing the following:
cd packages/Python/lldbsuite/test_event
python -m unittest discover -s test/src -p 'Test*.py'
Those tests run the dotest inferior with a known broken test and verify that the errors are caught. These tests did not pass until I modified dotest.py to capture them properly.
@zturner, if you have the chance, if you could try those steps above (the python -m unittest ... line) on Windows, that would be great if we can address any python2/3/Windows bits there. I don't think there's anything fancy, but I didn't want to hook it into test flow until I know it works there.
I'll be slowly adding more tests that cover some of the other breakage I've occasionally seen that didn't get collected as part of the summarization. This is the biggest one I'm aware of.
Reviewers: zturner, labath
Subscribers: zturner, lldb-commits
Differential Revision: http://reviews.llvm.org/D20193
llvm-svn: 269489
2016-05-14 05:36:26 +08:00
|
|
|
|
|
|
|
def visit_file(dir, name):
|
|
|
|
# Try to match the regexp pattern, if specified.
|
|
|
|
if configuration.regexp:
|
|
|
|
if not re.search(configuration.regexp, name):
|
|
|
|
# We didn't match the regex, we're done.
|
|
|
|
return
|
|
|
|
|
2016-10-05 02:48:00 +08:00
|
|
|
if configuration.skip_tests:
|
|
|
|
for file_regexp in configuration.skip_tests:
|
2016-09-24 05:32:47 +08:00
|
|
|
if re.search(file_regexp, name):
|
|
|
|
return
|
|
|
|
|
test infra: catch bad decorators and import-time errors
Summary:
This change enhances the LLDB test infrastructure to convert
load-time exceptions in a given Python test module into errors.
Before this change, specifying a non-existent test decorator,
or otherwise having some load-time error in a python test module,
would not get flagged as an error.
With this change, typos and other load-time errors in a python
test file get converted to errors and reported by the
test runner.
This change also includes test infrastructure tests that include
covering the new work here. I'm going to wait until we have
these infrastructure tests runnable on the main platforms before
I try to work that into all the normal testing workflows.
The test infrastructure tests can be run by using the standard python module testing practice of doing the following:
cd packages/Python/lldbsuite/test_event
python -m unittest discover -s test/src -p 'Test*.py'
Those tests run the dotest inferior with a known broken test and verify that the errors are caught. These tests did not pass until I modified dotest.py to capture them properly.
@zturner, if you have the chance, if you could try those steps above (the python -m unittest ... line) on Windows, that would be great if we can address any python2/3/Windows bits there. I don't think there's anything fancy, but I didn't want to hook it into test flow until I know it works there.
I'll be slowly adding more tests that cover some of the other breakage I've occasionally seen that didn't get collected as part of the summarization. This is the biggest one I'm aware of.
Reviewers: zturner, labath
Subscribers: zturner, lldb-commits
Differential Revision: http://reviews.llvm.org/D20193
llvm-svn: 269489
2016-05-14 05:36:26 +08:00
|
|
|
# We found a match for our test. Add it to the suite.
|
|
|
|
|
|
|
|
# Update the sys.path first.
|
|
|
|
if not sys.path.count(dir):
|
|
|
|
sys.path.insert(0, dir)
|
|
|
|
base = os.path.splitext(name)[0]
|
|
|
|
|
|
|
|
# Thoroughly check the filterspec against the base module and admit
|
|
|
|
# the (base, filterspec) combination only when it makes sense.
|
2019-10-08 08:26:53 +08:00
|
|
|
|
|
|
|
def check(obj, parts):
|
test infra: catch bad decorators and import-time errors
Summary:
This change enhances the LLDB test infrastructure to convert
load-time exceptions in a given Python test module into errors.
Before this change, specifying a non-existent test decorator,
or otherwise having some load-time error in a python test module,
would not get flagged as an error.
With this change, typos and other load-time errors in a python
test file get converted to errors and reported by the
test runner.
This change also includes test infrastructure tests that include
covering the new work here. I'm going to wait until we have
these infrastructure tests runnable on the main platforms before
I try to work that into all the normal testing workflows.
The test infrastructure tests can be run by using the standard python module testing practice of doing the following:
cd packages/Python/lldbsuite/test_event
python -m unittest discover -s test/src -p 'Test*.py'
Those tests run the dotest inferior with a known broken test and verify that the errors are caught. These tests did not pass until I modified dotest.py to capture them properly.
@zturner, if you have the chance, if you could try those steps above (the python -m unittest ... line) on Windows, that would be great if we can address any python2/3/Windows bits there. I don't think there's anything fancy, but I didn't want to hook it into test flow until I know it works there.
I'll be slowly adding more tests that cover some of the other breakage I've occasionally seen that didn't get collected as part of the summarization. This is the biggest one I'm aware of.
Reviewers: zturner, labath
Subscribers: zturner, lldb-commits
Differential Revision: http://reviews.llvm.org/D20193
llvm-svn: 269489
2016-05-14 05:36:26 +08:00
|
|
|
for part in parts:
|
|
|
|
try:
|
|
|
|
parent, obj = obj, getattr(obj, part)
|
|
|
|
except AttributeError:
|
|
|
|
# The filterspec has failed.
|
2019-10-08 08:26:53 +08:00
|
|
|
return False
|
|
|
|
return True
|
|
|
|
|
|
|
|
module = __import__(base)
|
|
|
|
|
|
|
|
def iter_filters():
|
|
|
|
for filterspec in configuration.filters:
|
|
|
|
parts = filterspec.split('.')
|
|
|
|
if check(module, parts):
|
|
|
|
yield filterspec
|
|
|
|
elif parts[0] == base and len(parts) > 1 and check(module, parts[1:]):
|
|
|
|
yield '.'.join(parts[1:])
|
|
|
|
else:
|
|
|
|
for key,value in module.__dict__.items():
|
|
|
|
if check(value, parts):
|
|
|
|
yield key + '.' + filterspec
|
test infra: catch bad decorators and import-time errors
Summary:
This change enhances the LLDB test infrastructure to convert
load-time exceptions in a given Python test module into errors.
Before this change, specifying a non-existent test decorator,
or otherwise having some load-time error in a python test module,
would not get flagged as an error.
With this change, typos and other load-time errors in a python
test file get converted to errors and reported by the
test runner.
This change also includes test infrastructure tests that include
covering the new work here. I'm going to wait until we have
these infrastructure tests runnable on the main platforms before
I try to work that into all the normal testing workflows.
The test infrastructure tests can be run by using the standard python module testing practice of doing the following:
cd packages/Python/lldbsuite/test_event
python -m unittest discover -s test/src -p 'Test*.py'
Those tests run the dotest inferior with a known broken test and verify that the errors are caught. These tests did not pass until I modified dotest.py to capture them properly.
@zturner, if you have the chance, if you could try those steps above (the python -m unittest ... line) on Windows, that would be great if we can address any python2/3/Windows bits there. I don't think there's anything fancy, but I didn't want to hook it into test flow until I know it works there.
I'll be slowly adding more tests that cover some of the other breakage I've occasionally seen that didn't get collected as part of the summarization. This is the biggest one I'm aware of.
Reviewers: zturner, labath
Subscribers: zturner, lldb-commits
Differential Revision: http://reviews.llvm.org/D20193
llvm-svn: 269489
2016-05-14 05:36:26 +08:00
|
|
|
|
2019-10-08 08:26:53 +08:00
|
|
|
filtered = False
|
|
|
|
for filterspec in iter_filters():
|
|
|
|
filtered = True
|
|
|
|
print("adding filter spec %s to module %s" % (filterspec, repr(module)))
|
|
|
|
tests = unittest2.defaultTestLoader.loadTestsFromName(filterspec, module)
|
|
|
|
configuration.suite.addTests(tests)
|
test infra: catch bad decorators and import-time errors
Summary:
This change enhances the LLDB test infrastructure to convert
load-time exceptions in a given Python test module into errors.
Before this change, specifying a non-existent test decorator,
or otherwise having some load-time error in a python test module,
would not get flagged as an error.
With this change, typos and other load-time errors in a python
test file get converted to errors and reported by the
test runner.
This change also includes test infrastructure tests that include
covering the new work here. I'm going to wait until we have
these infrastructure tests runnable on the main platforms before
I try to work that into all the normal testing workflows.
The test infrastructure tests can be run by using the standard python module testing practice of doing the following:
cd packages/Python/lldbsuite/test_event
python -m unittest discover -s test/src -p 'Test*.py'
Those tests run the dotest inferior with a known broken test and verify that the errors are caught. These tests did not pass until I modified dotest.py to capture them properly.
@zturner, if you have the chance, if you could try those steps above (the python -m unittest ... line) on Windows, that would be great if we can address any python2/3/Windows bits there. I don't think there's anything fancy, but I didn't want to hook it into test flow until I know it works there.
I'll be slowly adding more tests that cover some of the other breakage I've occasionally seen that didn't get collected as part of the summarization. This is the biggest one I'm aware of.
Reviewers: zturner, labath
Subscribers: zturner, lldb-commits
Differential Revision: http://reviews.llvm.org/D20193
llvm-svn: 269489
2016-05-14 05:36:26 +08:00
|
|
|
|
|
|
|
# Forgo this module if the (base, filterspec) combo is invalid
|
|
|
|
if configuration.filters and not filtered:
|
|
|
|
return
|
|
|
|
|
2019-10-08 08:26:53 +08:00
|
|
|
if not filtered:
|
test infra: catch bad decorators and import-time errors
Summary:
This change enhances the LLDB test infrastructure to convert
load-time exceptions in a given Python test module into errors.
Before this change, specifying a non-existent test decorator,
or otherwise having some load-time error in a python test module,
would not get flagged as an error.
With this change, typos and other load-time errors in a python
test file get converted to errors and reported by the
test runner.
This change also includes test infrastructure tests that include
covering the new work here. I'm going to wait until we have
these infrastructure tests runnable on the main platforms before
I try to work that into all the normal testing workflows.
The test infrastructure tests can be run by using the standard python module testing practice of doing the following:
cd packages/Python/lldbsuite/test_event
python -m unittest discover -s test/src -p 'Test*.py'
Those tests run the dotest inferior with a known broken test and verify that the errors are caught. These tests did not pass until I modified dotest.py to capture them properly.
@zturner, if you have the chance, if you could try those steps above (the python -m unittest ... line) on Windows, that would be great if we can address any python2/3/Windows bits there. I don't think there's anything fancy, but I didn't want to hook it into test flow until I know it works there.
I'll be slowly adding more tests that cover some of the other breakage I've occasionally seen that didn't get collected as part of the summarization. This is the biggest one I'm aware of.
Reviewers: zturner, labath
Subscribers: zturner, lldb-commits
Differential Revision: http://reviews.llvm.org/D20193
llvm-svn: 269489
2016-05-14 05:36:26 +08:00
|
|
|
# Add the entire file's worth of tests since we're not filtered.
|
|
|
|
# Also the fail-over case when the filterspec branch
|
|
|
|
# (base, filterspec) combo doesn't make sense.
|
|
|
|
configuration.suite.addTests(
|
|
|
|
unittest2.defaultTestLoader.loadTestsFromName(base))
|
|
|
|
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def visit(prefix, dir, names):
|
|
|
|
"""Visitor function for os.path.walk(path, visit, arg)."""
|
|
|
|
|
2015-12-09 04:36:22 +08:00
|
|
|
dir_components = set(dir.split(os.sep))
|
|
|
|
excluded_components = set(['.svn', '.git'])
|
|
|
|
if dir_components.intersection(excluded_components):
|
2015-10-29 01:43:26 +08:00
|
|
|
return
|
|
|
|
|
test infra: catch bad decorators and import-time errors
Summary:
This change enhances the LLDB test infrastructure to convert
load-time exceptions in a given Python test module into errors.
Before this change, specifying a non-existent test decorator,
or otherwise having some load-time error in a python test module,
would not get flagged as an error.
With this change, typos and other load-time errors in a python
test file get converted to errors and reported by the
test runner.
This change also includes test infrastructure tests that include
covering the new work here. I'm going to wait until we have
these infrastructure tests runnable on the main platforms before
I try to work that into all the normal testing workflows.
The test infrastructure tests can be run by using the standard python module testing practice of doing the following:
cd packages/Python/lldbsuite/test_event
python -m unittest discover -s test/src -p 'Test*.py'
Those tests run the dotest inferior with a known broken test and verify that the errors are caught. These tests did not pass until I modified dotest.py to capture them properly.
@zturner, if you have the chance, if you could try those steps above (the python -m unittest ... line) on Windows, that would be great if we can address any python2/3/Windows bits there. I don't think there's anything fancy, but I didn't want to hook it into test flow until I know it works there.
I'll be slowly adding more tests that cover some of the other breakage I've occasionally seen that didn't get collected as part of the summarization. This is the biggest one I'm aware of.
Reviewers: zturner, labath
Subscribers: zturner, lldb-commits
Differential Revision: http://reviews.llvm.org/D20193
llvm-svn: 269489
2016-05-14 05:36:26 +08:00
|
|
|
# Gather all the Python test file names that follow the Test*.py pattern.
|
|
|
|
python_test_files = [
|
|
|
|
name
|
|
|
|
for name in names
|
|
|
|
if name.endswith('.py') and name.startswith(prefix)]
|
|
|
|
|
|
|
|
# Visit all the python test files.
|
|
|
|
for name in python_test_files:
|
2020-07-20 22:52:38 +08:00
|
|
|
# Ensure we error out if we have multiple tests with the same
|
|
|
|
# base name.
|
|
|
|
# Future improvement: find all the places where we work with base
|
|
|
|
# names and convert to full paths. We have directory structure
|
|
|
|
# to disambiguate these, so we shouldn't need this constraint.
|
|
|
|
if name in configuration.all_tests:
|
|
|
|
raise Exception("Found multiple tests with the name %s" % name)
|
|
|
|
configuration.all_tests.add(name)
|
|
|
|
|
|
|
|
# Run the relevant tests in the python file.
|
|
|
|
visit_file(dir, name)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
|
|
|
|
# ======================================== #
|
|
|
|
# #
|
|
|
|
# Execution of the test driver starts here #
|
|
|
|
# #
|
|
|
|
# ======================================== #
|
|
|
|
|
2016-09-07 04:57:50 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def checkDsymForUUIDIsNotOn():
|
|
|
|
cmd = ["defaults", "read", "com.apple.DebugSymbols"]
|
2019-01-10 09:15:18 +08:00
|
|
|
process = subprocess.Popen(
|
2015-10-29 01:43:26 +08:00
|
|
|
cmd,
|
|
|
|
stdout=subprocess.PIPE,
|
|
|
|
stderr=subprocess.STDOUT)
|
2019-01-10 09:15:18 +08:00
|
|
|
cmd_output = process.stdout.read()
|
|
|
|
output_str = cmd_output.decode("utf-8")
|
|
|
|
if "DBGFileMappedPaths = " in output_str:
|
2015-10-29 01:43:26 +08:00
|
|
|
print("%s =>" % ' '.join(cmd))
|
2019-01-10 09:15:18 +08:00
|
|
|
print(output_str)
|
2015-10-29 01:43:26 +08:00
|
|
|
print(
|
|
|
|
"Disable automatic lookup and caching of dSYMs before running the test suite!")
|
|
|
|
print("Exiting...")
|
|
|
|
sys.exit(0)
|
|
|
|
|
2016-09-07 04:57:50 +08:00
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def exitTestSuite(exitCode=None):
|
2020-03-05 15:12:54 +08:00
|
|
|
# lldb.py does SBDebugger.Initialize().
|
|
|
|
# Call SBDebugger.Terminate() on exit.
|
2015-10-29 01:43:26 +08:00
|
|
|
import lldb
|
|
|
|
lldb.SBDebugger.Terminate()
|
|
|
|
if exitCode:
|
|
|
|
sys.exit(exitCode)
|
|
|
|
|
|
|
|
|
2015-11-05 08:46:25 +08:00
|
|
|
def getVersionForSDK(sdk):
|
|
|
|
sdk = str.lower(sdk)
|
|
|
|
full_path = seven.get_command_output('xcrun -sdk %s --show-sdk-path' % sdk)
|
|
|
|
basename = os.path.basename(full_path)
|
|
|
|
basename = os.path.splitext(basename)[0]
|
|
|
|
basename = str.lower(basename)
|
|
|
|
ver = basename.replace(sdk, '')
|
|
|
|
return ver
|
|
|
|
|
2016-09-07 04:57:50 +08:00
|
|
|
|
2017-03-15 16:51:59 +08:00
|
|
|
def checkCompiler():
|
|
|
|
# Add some intervention here to sanity check that the compiler requested is sane.
|
|
|
|
# If found not to be an executable program, we abort.
|
|
|
|
c = configuration.compiler
|
|
|
|
if which(c):
|
|
|
|
return
|
|
|
|
|
|
|
|
if not sys.platform.startswith("darwin"):
|
|
|
|
raise Exception(c + " is not a valid compiler")
|
|
|
|
|
|
|
|
pipe = subprocess.Popen(
|
|
|
|
['xcrun', '-find', c], stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
|
|
|
|
cmd_output = pipe.stdout.read()
|
|
|
|
if not cmd_output or "not found" in cmd_output:
|
|
|
|
raise Exception(c + " is not a valid compiler")
|
|
|
|
|
|
|
|
configuration.compiler = cmd_output.split('\n')[0]
|
|
|
|
print("'xcrun -find %s' returning %s" % (c, configuration.compiler))
|
|
|
|
|
Centralize libc++ test skipping logic
Summary:
This aims to replace the different decorators we've had on each libc++
test with a single solution. Each libc++ will be assigned to the
"libc++" category and a single central piece of code will decide whether
we are actually able to run libc++ test in the given configuration by
enabling or disabling the category (while giving the user the
opportunity to override this).
I started this effort because I wanted to get libc++ tests running on
android, and none of the existing decorators worked for this use case:
- skipIfGcc - incorrect, we can build libc++ executables on android
with gcc (in fact, after this, we can now do it on linux as well)
- lldbutil.skip_if_library_missing - this checks whether libc++.so is
loaded in the proces, which fails in case of a statically linked
libc++ (this makes copying executables to the remote target easier to
manage).
To make this work I needed to split out the pseudo_barrier code from the
force-included file, as libc++'s atomic does not play well with gcc on
linux, and this made every test fail, even though we need the code only
in the threading tests.
So far, I am only annotating one of the tests with this category. If
this does not break anything, I'll proceed to update the rest.
Reviewers: jingham, zturner, EricWF
Subscribers: srhines, lldb-commits
Differential Revision: https://reviews.llvm.org/D30984
llvm-svn: 299028
2017-03-30 05:01:14 +08:00
|
|
|
def canRunLibcxxTests():
|
|
|
|
from lldbsuite.test import lldbplatformutil
|
|
|
|
|
|
|
|
platform = lldbplatformutil.getPlatform()
|
|
|
|
|
|
|
|
if lldbplatformutil.target_is_android() or lldbplatformutil.platformIsDarwin():
|
|
|
|
return True, "libc++ always present"
|
|
|
|
|
|
|
|
if platform == "linux":
|
2019-12-11 08:48:33 +08:00
|
|
|
if os.path.isdir("/usr/include/c++/v1"):
|
|
|
|
return True, "Headers found, let's hope they work"
|
|
|
|
with tempfile.NamedTemporaryFile() as f:
|
|
|
|
cmd = [configuration.compiler, "-xc++", "-stdlib=libc++", "-o", f.name, "-"]
|
|
|
|
p = subprocess.Popen(cmd, stdin=subprocess.PIPE, stdout=subprocess.PIPE, stderr=subprocess.PIPE, universal_newlines=True)
|
2019-12-12 06:02:22 +08:00
|
|
|
_, stderr = p.communicate("#include <algorithm>\nint main() {}")
|
2019-12-11 08:48:33 +08:00
|
|
|
if not p.returncode:
|
|
|
|
return True, "Compiling with -stdlib=libc++ works"
|
|
|
|
return False, "Compiling with -stdlib=libc++ fails with the error: %s" % stderr
|
Centralize libc++ test skipping logic
Summary:
This aims to replace the different decorators we've had on each libc++
test with a single solution. Each libc++ will be assigned to the
"libc++" category and a single central piece of code will decide whether
we are actually able to run libc++ test in the given configuration by
enabling or disabling the category (while giving the user the
opportunity to override this).
I started this effort because I wanted to get libc++ tests running on
android, and none of the existing decorators worked for this use case:
- skipIfGcc - incorrect, we can build libc++ executables on android
with gcc (in fact, after this, we can now do it on linux as well)
- lldbutil.skip_if_library_missing - this checks whether libc++.so is
loaded in the proces, which fails in case of a statically linked
libc++ (this makes copying executables to the remote target easier to
manage).
To make this work I needed to split out the pseudo_barrier code from the
force-included file, as libc++'s atomic does not play well with gcc on
linux, and this made every test fail, even though we need the code only
in the threading tests.
So far, I am only annotating one of the tests with this category. If
this does not break anything, I'll proceed to update the rest.
Reviewers: jingham, zturner, EricWF
Subscribers: srhines, lldb-commits
Differential Revision: https://reviews.llvm.org/D30984
llvm-svn: 299028
2017-03-30 05:01:14 +08:00
|
|
|
|
|
|
|
return False, "Don't know how to build with libc++ on %s" % platform
|
|
|
|
|
|
|
|
def checkLibcxxSupport():
|
|
|
|
result, reason = canRunLibcxxTests()
|
|
|
|
if result:
|
|
|
|
return # libc++ supported
|
2019-12-12 19:17:14 +08:00
|
|
|
if "libc++" in configuration.categories_list:
|
Centralize libc++ test skipping logic
Summary:
This aims to replace the different decorators we've had on each libc++
test with a single solution. Each libc++ will be assigned to the
"libc++" category and a single central piece of code will decide whether
we are actually able to run libc++ test in the given configuration by
enabling or disabling the category (while giving the user the
opportunity to override this).
I started this effort because I wanted to get libc++ tests running on
android, and none of the existing decorators worked for this use case:
- skipIfGcc - incorrect, we can build libc++ executables on android
with gcc (in fact, after this, we can now do it on linux as well)
- lldbutil.skip_if_library_missing - this checks whether libc++.so is
loaded in the proces, which fails in case of a statically linked
libc++ (this makes copying executables to the remote target easier to
manage).
To make this work I needed to split out the pseudo_barrier code from the
force-included file, as libc++'s atomic does not play well with gcc on
linux, and this made every test fail, even though we need the code only
in the threading tests.
So far, I am only annotating one of the tests with this category. If
this does not break anything, I'll proceed to update the rest.
Reviewers: jingham, zturner, EricWF
Subscribers: srhines, lldb-commits
Differential Revision: https://reviews.llvm.org/D30984
llvm-svn: 299028
2017-03-30 05:01:14 +08:00
|
|
|
return # libc++ category explicitly requested, let it run.
|
|
|
|
print("Libc++ tests will not be run because: " + reason)
|
2019-12-12 19:17:14 +08:00
|
|
|
configuration.skip_categories.append("libc++")
|
2017-03-15 16:51:59 +08:00
|
|
|
|
2018-07-11 04:37:24 +08:00
|
|
|
def canRunLibstdcxxTests():
|
|
|
|
from lldbsuite.test import lldbplatformutil
|
|
|
|
|
|
|
|
platform = lldbplatformutil.getPlatform()
|
2019-07-23 08:28:26 +08:00
|
|
|
if lldbplatformutil.target_is_android():
|
|
|
|
platform = "android"
|
2018-07-11 04:37:24 +08:00
|
|
|
if platform == "linux":
|
2019-07-23 08:28:26 +08:00
|
|
|
return True, "libstdcxx always present"
|
2018-07-11 04:37:24 +08:00
|
|
|
return False, "Don't know how to build with libstdcxx on %s" % platform
|
|
|
|
|
|
|
|
def checkLibstdcxxSupport():
|
|
|
|
result, reason = canRunLibstdcxxTests()
|
|
|
|
if result:
|
|
|
|
return # libstdcxx supported
|
2019-12-12 19:17:14 +08:00
|
|
|
if "libstdcxx" in configuration.categories_list:
|
2018-07-11 04:37:24 +08:00
|
|
|
return # libstdcxx category explicitly requested, let it run.
|
|
|
|
print("libstdcxx tests will not be run because: " + reason)
|
2019-12-12 19:17:14 +08:00
|
|
|
configuration.skip_categories.append("libstdcxx")
|
2018-07-11 04:37:24 +08:00
|
|
|
|
2019-06-17 17:49:05 +08:00
|
|
|
def canRunWatchpointTests():
|
|
|
|
from lldbsuite.test import lldbplatformutil
|
|
|
|
|
|
|
|
platform = lldbplatformutil.getPlatform()
|
|
|
|
if platform == "netbsd":
|
2019-08-30 02:37:05 +08:00
|
|
|
if os.geteuid() == 0:
|
|
|
|
return True, "root can always write dbregs"
|
|
|
|
try:
|
|
|
|
output = subprocess.check_output(["/sbin/sysctl", "-n",
|
|
|
|
"security.models.extensions.user_set_dbregs"]).decode().strip()
|
|
|
|
if output == "1":
|
|
|
|
return True, "security.models.extensions.user_set_dbregs enabled"
|
|
|
|
except subprocess.CalledProcessError:
|
|
|
|
pass
|
|
|
|
return False, "security.models.extensions.user_set_dbregs disabled"
|
2019-06-17 17:49:05 +08:00
|
|
|
return True, "watchpoint support available"
|
|
|
|
|
|
|
|
def checkWatchpointSupport():
|
|
|
|
result, reason = canRunWatchpointTests()
|
|
|
|
if result:
|
|
|
|
return # watchpoints supported
|
2019-12-12 19:17:14 +08:00
|
|
|
if "watchpoint" in configuration.categories_list:
|
2019-06-17 17:49:05 +08:00
|
|
|
return # watchpoint category explicitly requested, let it run.
|
|
|
|
print("watchpoint tests will not be run because: " + reason)
|
2019-12-12 19:17:14 +08:00
|
|
|
configuration.skip_categories.append("watchpoint")
|
2019-06-17 17:49:05 +08:00
|
|
|
|
2020-11-09 17:47:22 +08:00
|
|
|
def checkObjcSupport():
|
|
|
|
from lldbsuite.test import lldbplatformutil
|
|
|
|
|
|
|
|
if not lldbplatformutil.platformIsDarwin():
|
|
|
|
print("objc tests will be skipped because of unsupported platform")
|
|
|
|
configuration.skip_categories.append("objc")
|
|
|
|
|
2018-04-24 18:51:44 +08:00
|
|
|
def checkDebugInfoSupport():
|
|
|
|
import lldb
|
|
|
|
|
2020-03-05 15:12:54 +08:00
|
|
|
platform = lldb.selected_platform.GetTriple().split('-')[2]
|
2018-04-24 18:51:44 +08:00
|
|
|
compiler = configuration.compiler
|
|
|
|
skipped = []
|
|
|
|
for cat in test_categories.debug_info_categories:
|
2019-12-12 19:17:14 +08:00
|
|
|
if cat in configuration.categories_list:
|
2018-04-24 18:51:44 +08:00
|
|
|
continue # Category explicitly requested, let it run.
|
|
|
|
if test_categories.is_supported_on_platform(cat, platform, compiler):
|
|
|
|
continue
|
2019-12-12 19:17:14 +08:00
|
|
|
configuration.skip_categories.append(cat)
|
2018-04-24 18:51:44 +08:00
|
|
|
skipped.append(cat)
|
|
|
|
if skipped:
|
|
|
|
print("Skipping following debug info categories:", skipped)
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
def run_suite():
|
|
|
|
# On MacOS X, check to make sure that domain for com.apple.DebugSymbols defaults
|
|
|
|
# does not exist before proceeding to running the test suite.
|
|
|
|
if sys.platform.startswith("darwin"):
|
|
|
|
checkDsymForUUIDIsNotOn()
|
|
|
|
|
|
|
|
# Start the actions by first parsing the options while setting up the test
|
|
|
|
# directories, followed by setting up the search paths for lldb utilities;
|
|
|
|
# then, we walk the directory trees and collect the tests into our test suite.
|
|
|
|
#
|
|
|
|
parseOptionsAndInitTestdirs()
|
|
|
|
|
2020-09-17 05:26:40 +08:00
|
|
|
# Print a stack trace if the test hangs or is passed SIGTERM.
|
|
|
|
registerFaulthandler()
|
|
|
|
|
2015-10-29 01:43:26 +08:00
|
|
|
setupSysPath()
|
|
|
|
|
2020-04-09 06:34:13 +08:00
|
|
|
import lldbconfig
|
2020-04-14 23:41:50 +08:00
|
|
|
if configuration.capture_path or configuration.replay_path:
|
|
|
|
lldbconfig.INITIALIZE = False
|
2015-10-29 01:43:26 +08:00
|
|
|
import lldb
|
2020-04-09 06:34:13 +08:00
|
|
|
|
2020-04-14 23:41:50 +08:00
|
|
|
if configuration.capture_path:
|
|
|
|
lldb.SBReproducer.Capture(configuration.capture_path)
|
|
|
|
lldb.SBReproducer.SetAutoGenerate(True)
|
|
|
|
elif configuration.replay_path:
|
|
|
|
lldb.SBReproducer.PassiveReplay(configuration.replay_path)
|
|
|
|
|
|
|
|
if not lldbconfig.INITIALIZE:
|
|
|
|
lldb.SBDebugger.Initialize()
|
|
|
|
|
2020-03-05 15:12:54 +08:00
|
|
|
# Use host platform by default.
|
|
|
|
lldb.selected_platform = lldb.SBPlatform.GetHostPlatform()
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2019-08-29 04:54:17 +08:00
|
|
|
# Now we can also import lldbutil
|
|
|
|
from lldbsuite.test import lldbutil
|
|
|
|
|
2015-12-08 09:15:30 +08:00
|
|
|
if configuration.lldb_platform_name:
|
|
|
|
print("Setting up remote platform '%s'" %
|
|
|
|
(configuration.lldb_platform_name))
|
|
|
|
lldb.remote_platform = lldb.SBPlatform(
|
|
|
|
configuration.lldb_platform_name)
|
2015-10-29 01:43:26 +08:00
|
|
|
if not lldb.remote_platform.IsValid():
|
2015-12-08 09:15:30 +08:00
|
|
|
print(
|
|
|
|
"error: unable to create the LLDB platform named '%s'." %
|
|
|
|
(configuration.lldb_platform_name))
|
2015-10-29 01:43:26 +08:00
|
|
|
exitTestSuite(1)
|
2015-12-08 09:15:30 +08:00
|
|
|
if configuration.lldb_platform_url:
|
2015-10-29 01:43:26 +08:00
|
|
|
# We must connect to a remote platform if a LLDB platform URL was
|
|
|
|
# specified
|
2015-12-08 09:15:30 +08:00
|
|
|
print(
|
|
|
|
"Connecting to remote platform '%s' at '%s'..." %
|
|
|
|
(configuration.lldb_platform_name, configuration.lldb_platform_url))
|
|
|
|
platform_connect_options = lldb.SBPlatformConnectOptions(
|
|
|
|
configuration.lldb_platform_url)
|
2015-10-29 01:43:26 +08:00
|
|
|
err = lldb.remote_platform.ConnectRemote(platform_connect_options)
|
|
|
|
if err.Success():
|
|
|
|
print("Connected.")
|
|
|
|
else:
|
2015-12-08 09:15:30 +08:00
|
|
|
print("error: failed to connect to remote platform using URL '%s': %s" % (
|
|
|
|
configuration.lldb_platform_url, err))
|
2015-10-29 01:43:26 +08:00
|
|
|
exitTestSuite(1)
|
|
|
|
else:
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.lldb_platform_url = None
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2015-12-08 09:15:30 +08:00
|
|
|
if configuration.lldb_platform_working_dir:
|
|
|
|
print("Setting remote platform working directory to '%s'..." %
|
|
|
|
(configuration.lldb_platform_working_dir))
|
2017-03-21 00:07:17 +08:00
|
|
|
error = lldb.remote_platform.MakeDirectory(
|
|
|
|
configuration.lldb_platform_working_dir, 448) # 448 = 0o700
|
|
|
|
if error.Fail():
|
|
|
|
raise Exception("making remote directory '%s': %s" % (
|
2018-05-09 23:35:19 +08:00
|
|
|
configuration.lldb_platform_working_dir, error))
|
2017-03-21 00:07:17 +08:00
|
|
|
|
|
|
|
if not lldb.remote_platform.SetWorkingDirectory(
|
|
|
|
configuration.lldb_platform_working_dir):
|
2018-05-09 23:35:19 +08:00
|
|
|
raise Exception("failed to set working directory '%s'" % configuration.lldb_platform_working_dir)
|
2020-03-05 15:12:54 +08:00
|
|
|
lldb.selected_platform = lldb.remote_platform
|
2015-10-29 01:43:26 +08:00
|
|
|
else:
|
|
|
|
lldb.remote_platform = None
|
2015-12-08 09:15:30 +08:00
|
|
|
configuration.lldb_platform_working_dir = None
|
|
|
|
configuration.lldb_platform_url = None
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2018-01-31 02:29:16 +08:00
|
|
|
# Set up the working directory.
|
|
|
|
# Note that it's not dotest's job to clean this directory.
|
2020-06-03 07:49:03 +08:00
|
|
|
lldbutil.mkdir_p(configuration.test_build_dir)
|
2018-02-02 06:18:02 +08:00
|
|
|
|
2020-11-06 04:24:56 +08:00
|
|
|
from . import lldbplatformutil
|
|
|
|
target_platform = lldbplatformutil.getPlatform()
|
2015-10-29 01:43:26 +08:00
|
|
|
|
Centralize libc++ test skipping logic
Summary:
This aims to replace the different decorators we've had on each libc++
test with a single solution. Each libc++ will be assigned to the
"libc++" category and a single central piece of code will decide whether
we are actually able to run libc++ test in the given configuration by
enabling or disabling the category (while giving the user the
opportunity to override this).
I started this effort because I wanted to get libc++ tests running on
android, and none of the existing decorators worked for this use case:
- skipIfGcc - incorrect, we can build libc++ executables on android
with gcc (in fact, after this, we can now do it on linux as well)
- lldbutil.skip_if_library_missing - this checks whether libc++.so is
loaded in the proces, which fails in case of a statically linked
libc++ (this makes copying executables to the remote target easier to
manage).
To make this work I needed to split out the pseudo_barrier code from the
force-included file, as libc++'s atomic does not play well with gcc on
linux, and this made every test fail, even though we need the code only
in the threading tests.
So far, I am only annotating one of the tests with this category. If
this does not break anything, I'll proceed to update the rest.
Reviewers: jingham, zturner, EricWF
Subscribers: srhines, lldb-commits
Differential Revision: https://reviews.llvm.org/D30984
llvm-svn: 299028
2017-03-30 05:01:14 +08:00
|
|
|
checkLibcxxSupport()
|
2018-07-11 04:37:24 +08:00
|
|
|
checkLibstdcxxSupport()
|
2019-06-17 17:49:05 +08:00
|
|
|
checkWatchpointSupport()
|
2018-04-24 18:51:44 +08:00
|
|
|
checkDebugInfoSupport()
|
2020-11-09 17:47:22 +08:00
|
|
|
checkObjcSupport()
|
Centralize libc++ test skipping logic
Summary:
This aims to replace the different decorators we've had on each libc++
test with a single solution. Each libc++ will be assigned to the
"libc++" category and a single central piece of code will decide whether
we are actually able to run libc++ test in the given configuration by
enabling or disabling the category (while giving the user the
opportunity to override this).
I started this effort because I wanted to get libc++ tests running on
android, and none of the existing decorators worked for this use case:
- skipIfGcc - incorrect, we can build libc++ executables on android
with gcc (in fact, after this, we can now do it on linux as well)
- lldbutil.skip_if_library_missing - this checks whether libc++.so is
loaded in the proces, which fails in case of a statically linked
libc++ (this makes copying executables to the remote target easier to
manage).
To make this work I needed to split out the pseudo_barrier code from the
force-included file, as libc++'s atomic does not play well with gcc on
linux, and this made every test fail, even though we need the code only
in the threading tests.
So far, I am only annotating one of the tests with this category. If
this does not break anything, I'll proceed to update the rest.
Reviewers: jingham, zturner, EricWF
Subscribers: srhines, lldb-commits
Differential Revision: https://reviews.llvm.org/D30984
llvm-svn: 299028
2017-03-30 05:01:14 +08:00
|
|
|
|
2020-11-06 04:24:56 +08:00
|
|
|
# Perform LLGS tests only on platforms using it.
|
|
|
|
configuration.llgs_platform = (
|
|
|
|
target_platform in ["freebsd", "linux", "netbsd", "windows"])
|
|
|
|
|
|
|
|
# Perform debugserver tests elsewhere (i.e. on Darwin platforms).
|
|
|
|
configuration.debugserver_platform = not configuration.llgs_platform
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2020-02-13 21:40:09 +08:00
|
|
|
for testdir in configuration.testdirs:
|
2015-11-05 09:33:54 +08:00
|
|
|
for (dirpath, dirnames, filenames) in os.walk(testdir):
|
|
|
|
visit('Test', dirpath, filenames)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
#
|
|
|
|
# Now that we have loaded all the test cases, run the whole test suite.
|
|
|
|
#
|
|
|
|
|
|
|
|
# Install the control-c handler.
|
|
|
|
unittest2.signals.installHandler()
|
|
|
|
|
|
|
|
#
|
2017-03-15 16:51:59 +08:00
|
|
|
# Invoke the default TextTestRunner to run the test suite
|
2015-10-29 01:43:26 +08:00
|
|
|
#
|
2017-03-15 16:51:59 +08:00
|
|
|
checkCompiler()
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2019-08-29 00:28:58 +08:00
|
|
|
if configuration.verbose:
|
2017-03-15 16:51:59 +08:00
|
|
|
print("compiler=%s" % configuration.compiler)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2017-03-15 16:51:59 +08:00
|
|
|
# Iterating over all possible architecture and compiler combinations.
|
|
|
|
configString = "arch=%s compiler=%s" % (configuration.arch,
|
|
|
|
configuration.compiler)
|
|
|
|
|
|
|
|
# Output the configuration.
|
2019-08-29 00:28:58 +08:00
|
|
|
if configuration.verbose:
|
2017-03-15 16:51:59 +08:00
|
|
|
sys.stderr.write("\nConfiguration: " + configString + "\n")
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2017-03-15 16:51:59 +08:00
|
|
|
# First, write out the number of collected test cases.
|
2019-08-29 00:28:58 +08:00
|
|
|
if configuration.verbose:
|
2017-03-15 16:51:59 +08:00
|
|
|
sys.stderr.write(configuration.separator + "\n")
|
|
|
|
sys.stderr.write(
|
|
|
|
"Collected %d test%s\n\n" %
|
|
|
|
(configuration.suite.countTestCases(),
|
|
|
|
configuration.suite.countTestCases() != 1 and "s" or ""))
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2020-08-29 05:27:37 +08:00
|
|
|
if configuration.suite.countTestCases() == 0:
|
|
|
|
logging.error("did not discover any matching tests")
|
|
|
|
exitTestSuite(1)
|
|
|
|
|
2017-03-15 16:51:59 +08:00
|
|
|
# Invoke the test runner.
|
|
|
|
if configuration.count == 1:
|
|
|
|
result = unittest2.TextTestRunner(
|
|
|
|
stream=sys.stderr,
|
2019-08-29 00:28:58 +08:00
|
|
|
verbosity=configuration.verbose,
|
2017-03-15 16:51:59 +08:00
|
|
|
resultclass=test_result.LLDBTestResult).run(
|
|
|
|
configuration.suite)
|
|
|
|
else:
|
|
|
|
# We are invoking the same test suite more than once. In this case,
|
|
|
|
# mark __ignore_singleton__ flag as True so the signleton pattern is
|
|
|
|
# not enforced.
|
|
|
|
test_result.LLDBTestResult.__ignore_singleton__ = True
|
|
|
|
for i in range(configuration.count):
|
|
|
|
|
|
|
|
result = unittest2.TextTestRunner(
|
|
|
|
stream=sys.stderr,
|
2019-08-29 00:28:58 +08:00
|
|
|
verbosity=configuration.verbose,
|
2017-03-15 16:51:59 +08:00
|
|
|
resultclass=test_result.LLDBTestResult).run(
|
|
|
|
configuration.suite)
|
|
|
|
|
|
|
|
configuration.failed = not result.wasSuccessful()
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2019-08-29 00:28:58 +08:00
|
|
|
if configuration.sdir_has_content and configuration.verbose:
|
2015-10-29 01:43:26 +08:00
|
|
|
sys.stderr.write(
|
|
|
|
"Session logs for test failures/errors/unexpected successes"
|
2020-12-04 18:42:36 +08:00
|
|
|
" can be found in the test build directory\n")
|
2015-10-29 01:43:26 +08:00
|
|
|
|
2019-12-12 19:17:14 +08:00
|
|
|
if configuration.use_categories and len(
|
|
|
|
configuration.failures_per_category) > 0:
|
2015-10-29 01:43:26 +08:00
|
|
|
sys.stderr.write("Failures per category:\n")
|
2019-12-12 19:17:14 +08:00
|
|
|
for category in configuration.failures_per_category:
|
2015-12-08 09:15:30 +08:00
|
|
|
sys.stderr.write(
|
|
|
|
"%s - %d\n" %
|
2019-12-12 19:17:14 +08:00
|
|
|
(category, configuration.failures_per_category[category]))
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
# Exiting.
|
2015-12-08 09:15:30 +08:00
|
|
|
exitTestSuite(configuration.failed)
|
2015-10-29 01:43:26 +08:00
|
|
|
|
|
|
|
if __name__ == "__main__":
|
2015-11-03 03:19:49 +08:00
|
|
|
print(
|
|
|
|
__file__ +
|
|
|
|
" is for use as a module only. It should not be run as a standalone script.")
|
|
|
|
sys.exit(-1)
|