LLDB test failures while building Swift 5.0 toolchain

stamba · December 20, 2018, 4:53am

LLDB test failures while building Swift 5.0 toolchain.

Sample test failure:-

Testing: 0 .
FAIL: lldb-Suite :: benchmarks/disassembly/TestXcode41Vs42GDBDisassembly.py (116 of 1566)
******************** TEST 'lldb-Suite :: benchmarks/disassembly/TestXcode41Vs42GDBDisassembly.py' FAILED ********************
lldb version 7.0.0 (GitHub - apple/swift-lldb: This is the version of LLDB that supports the Swift programming language & REPL. revision 450ac50b3d6c87b246f22f6a883b15c02f372e0c)
Swift-5.0 (revision f6eeb3adca4f6ed7e66d4463883540c361e8f2cf)
clang revision ad7fb41b1dc11fb61584125212aec259ebc583db
llvm revision f63b283c7143aef31863d5915c28ee79ed390be3
LLDB library dir: /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/bin
LLDB import library dir: /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/bin
Traceback (most recent call last):
File "/root/swift-source/lldb/test/dotest.py", line 7, in
lldbsuite.test.run_suite()
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/dotest.py", line 1258, in run_suite
import lldb
File "/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lib/python3.5/site-packages/lldb/init.py", line 53, in
_lldb = swig_import_helper()
File "/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lib/python3.5/site-packages/lldb/init.py", line 49, in swig_import_helper
_mod = imp.load_module('_lldb', fp, pathname, description)
ImportError: dynamic module does not define init function (init_lldb)

Adrian_Prantl · December 20, 2018, 4:42pm

From the looks of it, the python bindings are either incomplete or you have some search path problem. As a starting point, I'd try importing the lldb module from within a python interpreter, and debug why that doesn't work.

stamba · December 21, 2018, 10:25am

Hi,

I have installed all the development dependencies as mentioned in https://github.com/apple/swift:-

sudo apt-get install git cmake ninja-build clang python uuid-dev libicu-dev icu-devtools libbsd-dev libedit-dev libxml2-dev libsqlite3-dev swig libpython-dev libncurses5-dev pkg-config libblocksruntime-dev libcurl4-openssl-dev systemtap-sdt-dev tzdata rsync

I also tried setting the PYTHONPATH as mentioned in:-

The problem still persists and affects around 865 tests due to this reason.

Let me know if I am missing anything else.

dcci · January 9, 2019, 5:24pm

Just set PYTHON_PATH to what lldb -P evaluates to.

e.g.

$ lldb -P
/Applications/Xcode3.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python
$ export PYTHONPATH="/Applications/Xcode3.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python"

Then open python and type
import lldb

Does that work? If not, you have an include problem. If that does, try to run some basic lldb python commands and see what happens (you can probably copy test cases bodies).

stamba · January 15, 2019, 4:53am

Hi @dcci ,

Thanks for the above suggestion, it worked!

Set the python path environment variable PYTHONPATH to what lldb -P evaluated to:-

root@877e1c79bb05:~# /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/bin/lldb -P
/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lib/python2.7/site-packages

root@877e1c79bb05:~# export PYTHONPATH="/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lib/python2.7/site-packages"

With this 865/883 failing test cases passed which previously failed with common errors as mentioned in previous comments above.

Current status of lldb test suite is as below:-
Expected Passes : 1402
Unsupported Tests : 49
Unexpected Failures: 127

Investigating on the failure test cases further.

Around 51 test cases fail due to the following errors:-

FAIL: test_dwarf (lldbsuite.test.lldbtest.TestArrayEnum)

Traceback (most recent call last):
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1744, in test_method
return attrvalue(self)
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/decorators.py", line 144, in wrapper
func(*args, **kwargs)
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/lldbinline.py", line 134, in _test
self.do_test()
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/lldbinline.py", line 161, in do_test
"inline test did not hit a single breakpoint")
AssertionError: False is not True : inline test did not hit a single breakpoint
Config=ppc64le-/root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/bin/clang-7

Let me know if anything looks familiar to you. Thanks!

dcci · January 15, 2019, 5:02pm

Looks like the inline category of tests is broken. I haven't seen this one earlier, but I do recommend to start debugging the python code responsible for this.
(Random guess, given some breakpoints are not hit, could be that the sources aren't built with -g).

stamba · January 17, 2019, 11:06am

Checked, sources are built with -g.

stamba · January 18, 2019, 9:39am

Current status of lldb test suite is as below:-
Expected Passes : 1402
Unsupported Tests : 49
Unexpected Failures: 127

Many of the remaining test cases throw up errors like below:-
Error Type 1(Approx 49 occurences):-

error: Couldn't lookup symbols:
swift_beginAccess
swift_endAccess
error: Couldn't lookup symbols:
swift_allocError
swift_getWitnessTable
swift_willThrow
error: Couldn't lookup symbols:
method descriptor for Swift.Hashable._rawHashValue(seed: Swift.Int) -> Swift.Int
method descriptor for Swift.Hashable.hash(into: inout Swift.Hasher) -> ()
method descriptor for Swift.Hashable.hashValue.getter : Swift.Int
protocol descriptor for Swift.Hashable
[...Many More...]

Error Type 2(Approx 51 occurences):-

AssertionError: False is not True : inline test did not hit a single breakpoint

Error Type 3(Approx 13 occurences):-

AssertionError: False is not True : Expected 1 thread to stop at breakpoint, 0 did.

Investigating on the failure test cases further.

Tried setting the appropriate environment variables like LD_LIBRARY_PATH, LIBRARY_PATH, PATH, etc, however they don't help much.

dcci · January 18, 2019, 4:38pm

In my experience this happens because the REPL doesn't know how to locate libswiftCore.so/dylib.

Can you make sure the RPATH of the repl_swift binary is set up correctly?
(points to something that contains libSwiftcore ?)

To test my theory you can run lldb --repl and type print() and see if you see the errors.

stamba · January 21, 2019, 7:14am

Hi @dcci ,

I looked around the internet and tried exporting the following environment variables with the paths containing 'libswiftCore.so' library:
LD_LIBRARY_PATH, LIBRARY_PATH, RPATH, RUNPATH, SWIFTPM_EMBED_RPATH, REPL_SWIFT_RPATH, DT_RUNPATH, DT_RPATH, DYLD_LIBRARY_PATH.

However even after setting the environment variables, I am still facing the error - "error: Couldn't lookup symbols:"

root@d75bebab716c:~# /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/bin/lldb --repl
Welcome to Swift version 5.0-dev (LLVM f63b283c71, Clang 41ac4c4262, Swift d4598ec15a).
Type :help for assistance.
1> print
error: Couldn't lookup symbols:
Swift.print(_: Any..., separator: Swift.String, terminator: Swift.String) -> ()
swift_beginAccess
swift_endAccess
swift_release

1> print("Hello World!")
error: Couldn't lookup symbols:
Swift.String.init(_builtinStringLiteral: Builtin.RawPointer, utf8CodeUnitCount: Builtin.Word, isASCII: Builtin.Int1) -> Swift.String
type metadata for Swift.String
Swift.allocateUninitializedArray(Builtin.Word) -> (Swift.Array , Builtin.RawPointer)
Swift.print(: Any..., separator: Swift.String, terminator: Swift.String) -> ()
type metadata for Any
swift_bridgeObjectRelease
swift_release

1>

Am I missing anything?

dcci · January 22, 2019, 4:25pm

Assuming you're building with Cmake, you can go in:
lldb/tools/repl/swift
and see in the CMakeList.txt file:

# Set the correct rpath to locate libswiftCore.
if (LLDB_BUILD_FRAMEWORK)
  set(CMAKE_EXE_LINKER_FLAGS "-Wl,-rpath \
      -Wl,${CMAKE_BINARY_DIR}/${LLDB_FRAMEWORK_INSTALL_DIR}/${LLDB_FRAMEWORK_RESOURCE_DIR}/Swift/macosx")
elseif( CMAKE_SYSTEM_NAME MATCHES "Linux" )
  # Set the correct rpath to locate libswiftCore
  set(CMAKE_EXE_LINKER_FLAGS "-Wl,-rpath,${CMAKE_BINARY_DIR}/../swift-linux-x86_64/lib${LLVM_LIBDIR_SUFFIX}/swift/linux -Wl,-ldl")
  set(CMAKE_INSTALL_RPATH "$ORIGIN/../lib/swift/linux:${CMAKE_INSTALL_RPATH}")
endif()

My wild guess here is that the -Wl,-rpath passed here is wrong. I would say the guess isn't that wild either, because, as you can see, the cmake bits hardcode the architecture, which doesn't match the one you're running on.

To see which RPATH is embedded in the binary generated, repl_swift, I do recommend to use readelf or objdump. BTW, if this is the issue, it would be great if we can get that fixed.

stamba · January 24, 2019, 12:29pm

Hi @dcci ,

Thanks for the inputs, I made the below changes in the CMakeList.txt:-

if (CMAKE_HOST_SYSTEM_PROCESSOR MATCHES "ppc64le")
set(CMAKE_EXE_LINKER_FLAGS "-Wl,-rpath,${CMAKE_BINARY_DIR}/../swift-linux-powerpc64le/lib${LLVM_LIBDIR_SUFFIX}/swift/linux/powerpc64le -Wl,-ldl")
else()
set(CMAKE_EXE_LINKER_FLAGS "-Wl,-rpath,${CMAKE_BINARY_DIR}/../swift-linux-x86_64/lib${LLVM_LIBDIR_SUFFIX}/swift/linux -Wl,-ldl")

With this the "error: Couldn't lookup symbols:" are no longer encountered, and the lldb test failure count has come down to 117 from earlier 127 failures.
However for tests I am still seeing errors like below:-

1.) AssertionError: False is not True : inline test did not hit a single breakpoint(51 Occurences)
2.) AssertionError: False is not True : Expected 1 thread to stop at breakpoint, 0 did.(13 Occurences)
3.) AssertionError: False is not True(39 Occurences)
4.) AssertionError: False is not True : Command 'bt
Error output:
error: invalid thread
' returns successfully
(1 Occurence)
5.) AssertionError: False is not True : Command 'frame variable -d run -- o
Error output:
error: invalid thread
' returns successfully
(1 Occurence)

Does anything look familiar or I am still missing something? :|

dcci · January 24, 2019, 4:30pm

I see the failures went down, can you submit a patch?

For the other failures, I'm afraid I can't be of much help.
From what I see you're debugging ppcle which is a very different architecture than the one most people run on. You might consider start debugging the failures, and ask here if you get stuck.

stamba · January 30, 2019, 10:57am

Trying a clean build on the latest swift master branch. However I am facing the following issue:-

Linking /root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/bin/swift-test
Linking /root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/bin/swift-run
Linking /root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/bin/swift-build
Linking /root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/bin/swift-package
--- bootstrap: note: building self-hosted 'swift-build': env SWIFT_EXEC=/root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/powerpc64le-unknown-linux/release/swiftc SWIFTPM_BUILD_DIR=/root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le SWIFTPM_BOOTSTRAP=1 /root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/powerpc64le-unknown-linux/release/swift-build-stage1 --disable-sandbox -Xlinker -rpath -Xlinker $ORIGIN/../lib/swift/linux -Xswiftc -Xcc -Xswiftc -DSPM_BUILD_IDENT=e49bb01 -Xswiftc -I/root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/lib/swift/linux/x86_64 -Xswiftc -Xcc -Xswiftc -F/root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/lib/swift/linux/x86_64 -Xswiftc -I/root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/lib/swift/linux/x86_64/dispatch -Xlinker -L/root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/lib/swift/linux -Xlinker -rpath -Xlinker /root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/.bootstrap/lib/swift/linux -Xswiftc -I/root/swift-source/build/buildbot_linux/llbuild-linux-powerpc64le/products/llbuildSwift -Xswiftc -I/root/swift-source/llbuild/products/libllbuild/include -Xlinker -rpath -Xlinker $ORIGIN/../lib/swift/pm/llbuild -Xlinker -L/root/swift-source/build/buildbot_linux/llbuild-linux-powerpc64le/lib -Xlinker -rpath -Xlinker /root/swift-source/build/buildbot_linux/llbuild-linux-powerpc64le/lib -Xswiftc -enable-testing --configuration release --build-tests
/root/swift-source/build/buildbot_linux/swiftpm-linux-powerpc64le/powerpc64le-unknown-linux/release/swift-build-stage1: error while loading shared libraries: libicui18nswift.so.61: cannot open shared object file: No such file or directory
--- bootstrap: error: build failed with exit status 127
Building the standard library for: swift-stdlib-linux-powerpc64le
Running Swift tests for: check-swift-all-linux-powerpc64le check-swift-all-optimize-linux-powerpc64le
./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting
./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting

spevans · January 30, 2019, 12:07pm

It looks like there is no libicu library, did you pass the --libicu argument to build-script to get it to build?

stamba · January 30, 2019, 12:22pm

I am using the build-toolchain script to build as below:-
./swift/utils/build-toolchain srtbundle --test

This was working fine as recently as yesterday, only failing during testing step at the lldb-suite related test suite.

spevans · January 30, 2019, 12:46pm

Maybe try deleting the build/buildbot_linux/libicu-linux-powerpc64le directory (or whatever the arch specific directory is called) and try building again, it looks to be using the buildbox_linux preset so should be included there.

stamba · January 31, 2019, 11:49am

Thanks @spevans, I did a clean build on another system and it proceeded smoothly.

stamba · January 31, 2019, 12:06pm

Hi @dcci ,

Out of the 109 remaining lldb related test failures I am seeing the following kind of errors for 107 tests. On careful observation I found that the --arch parameter passed to the dotest.py is empty. i.e. "Command invoked: /root/swift-source/lldb/test/dotest.py -q --arch= -s /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-traces".
Is this expected or this could be causing issues?

Detailed error is as below(seen for 107/109 failures):-

******************** TEST 'lldb-Suite :: lang/swift/archetype_resolution_subclass/TestArchetypeResolutionSubclass.py' FAILED ********************
lldb version 7.0.0 (GitHub - apple/swift-lldb: This is the version of LLDB that supports the Swift programming language & REPL. revision a6ad475f9ee5558baf6baf49e2be7b77ff46df5f)
Swift-5.0 (revision d29b545870946e72549ce2f32dfda8116ba5829f)
clang revision 38ef19dd1f3ea3d09a8b7e77b29aa95fd6ad7d87
llvm revision 28bfcfbd091e6112f164c00f9c555cd2cadfcc64
LLDB library dir: /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/bin
LLDB import library dir: /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/bin
Skipping following debug info categories: ['dsym', 'gmodules']

Session logs for test failures/errors/unexpected successes will go into directory '/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-traces'
Command invoked: /root/swift-source/lldb/test/dotest.py -q --arch= -s /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-traces --build-dir /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex -S nm -u CXXFLAGS -u CFLAGS --executable /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/./bin/lldb --dsymutil /root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/./bin/dsymutil --filecheck /root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/./bin/FileCheck -C /root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/bin/clang --swift-compiler /root/swift-source/build/buildbot_linux/swift-linux-powerpc64le/bin/swiftc --swift-library /root/swift-source/build/buildbot_linux/swift-linux-powerpc64le/lib/swift --env ARCHIVER=/usr/bin/ar --env OBJCOPY=/usr/bin/objcopy --build-dir /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex --test-subdir lang/swift --skip-category=watchpoint --skip-category=dwo -t -E -Xcc -F/root/swift-source/build/buildbot_linux/foundation-linux-powerpc64le/CoreFoundation-prefix/System/Library/Frameworks -I/root/swift-source/build/buildbot_linux/foundation-linux-powerpc64le/swift -I/root/swift-source/swift-corelibs-libdispatch -L/root/swift-source/build/buildbot_linux/foundation-linux-powerpc64le -L/root/swift-source/build/buildbot_linux/libdispatch-linux-powerpc64le -L/root/swift-source/build/buildbot_linux/libdispatch-linux-powerpc64le/src -Xlinker -rpath -Xlinker /root/swift-source/build/buildbot_linux/libdispatch-linux-powerpc64le/src -Xlinker -rpath -Xlinker /root/swift-source/build/buildbot_linux/libdispatch-linux-powerpc64le -Xlinker -rpath -Xlinker /root/swift-source/build/buildbot_linux/foundation-linux-powerpc64le /root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass -p TestArchetypeResolutionSubclass.py
Change dir to: /root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass
UNSUPPORTED: LLDB (/root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/bin/clang-7-ppc64le) :: test_dsym (lldbsuite.test.lldbtest.TestArchetypeResolutionSubclass) (test case does not fall in any category of interest for this run)
runCmd: settings set symbols.clang-modules-cache-path "/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/module-cache-lldb"
output: None

runCmd: settings set symbols.enable-external-lookup false
output: None

os command: make VPATH=/root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass -C /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/lang/swift/archetype_resolution_subclass/lldbsuite.test.lldbtest.test_dwarf -I /root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass -f /root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass/Makefile MAKE_DSYM=NO ARCH=ppc64le CC=/root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/bin/clang-7 SWIFTC=/root/swift-source/build/buildbot_linux/swift-linux-powerpc64le/bin/swiftc
with pid: 5241
stdout: make: Entering directory '/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/lang/swift/archetype_resolution_subclass/lldbsuite.test.lldbtest.test_dwarf'

Compiling /root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass/main.swift

/root/swift-source/build/buildbot_linux/swift-linux-powerpc64le/bin/swift -frontend -c -primary-file /root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass/main.swift

-g -Onone -serialize-debugging-options -module-cache-path /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/module-cache-clang -sdk / -enable-anonymous-context-mangled-names -module-name a -emit-module-path
/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/lang/swift/archetype_resolution_subclass/lldbsuite.test.lldbtest.test_dwarf/main.partial.swiftmodule
-o /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/lang/swift/archetype_resolution_subclass/lldbsuite.test.lldbtest.test_dwarf/main.o

Merging swift modules for a

/root/swift-source/build/buildbot_linux/swift-linux-powerpc64le/bin/swift -frontend -g -Onone -serialize-debugging-options -module-cache-path /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/module-cache-clang -sdk / -enable-anonymous-context-mangled-names -merge-modules
-emit-module main.partial.swiftmodule
-parse-as-library -sil-merge-partial-modules
-disable-diagnostic-passes -disable-sil-perf-optzns
-module-name a
-o /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/lang/swift/archetype_resolution_subclass/lldbsuite.test.lldbtest.test_dwarf/a.swiftmodule

Wrapping swift module

/root/swift-source/build/buildbot_linux/swift-linux-powerpc64le/bin/swift -modulewrap a.swiftmodule -o /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/lang/swift/archetype_resolution_subclass/lldbsuite.test.lldbtest.test_dwarf/a.swiftmodule.o

Linking a.out

/root/swift-source/build/buildbot_linux/swift-linux-powerpc64le/bin/swiftc a.swiftmodule.o main.o -Onone -Xfrontend -serialize-debugging-options -module-cache-path /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/module-cache-clang -sdk "/" -o "a.out"
make: Leaving directory '/root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/lldb-test-build.noindex/lang/swift/archetype_resolution_subclass/lldbsuite.test.lldbtest.test_dwarf'

stderr: /root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass/main.swift:11:1: warning: result of call to 'f' is unused
f(x)
^~~~

retcode: 0

FAIL: LLDB (/root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/bin/clang-7-ppc64le) :: test_dwarf (lldbsuite.test.lldbtest.TestArchetypeResolutionSubclass)
<bound method SBProcess.Kill of <lldb.SBProcess; proxy of <Swig Object of type 'lldb::SBProcess *' at 0x3fff767cee70> >>: success

UNSUPPORTED: LLDB (/root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/bin/clang-7-ppc64le) :: test_dwo (lldbsuite.test.lldbtest.TestArchetypeResolutionSubclass) (test case does not fall in any category of interest for this run)
UNSUPPORTED: LLDB (/root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/bin/clang-7-ppc64le) :: test_gmodules (lldbsuite.test.lldbtest.TestArchetypeResolutionSubclass) (test case does not fall in any category of interest for this run)
Restore dir to: /root/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/test-results

FAIL: test_dwarf (lldbsuite.test.lldbtest.TestArchetypeResolutionSubclass)

Traceback (most recent call last):
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1744, in test_method
return attrvalue(self)
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/decorators.py", line 144, in wrapper
func(*args, **kwargs)
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/lldbinline.py", line 134, in _test
self.do_test()
File "/root/swift-source/lldb/packages/Python/lldbsuite/test/lldbinline.py", line 161, in do_test
"inline test did not hit a single breakpoint")
AssertionError: False is not True : inline test did not hit a single breakpoint
Config=ppc64le-/root/swift-source/build/buildbot_linux/llvm-linux-powerpc64le/bin/clang-7

Ran 4 tests in 3.177s

RESULT: FAILED (0 passes, 1 failures, 0 errors, 3 skipped, 0 expected failures, 0 unexpected successes)

stamba · February 1, 2019, 5:10am

@spevans do you find anything familiar in the above error related to --arch parameter passed to the dotest.py being empty?

LLDB test failures while building Swift 5.0 toolchain

Around 51 test cases fail due to the following errors:-

FAIL: test_dwarf (lldbsuite.test.lldbtest.TestArrayEnum)

Many of the remaining test cases throw up errors like below:- Error Type 1(Approx 49 occurences):-

Error Type 2(Approx 51 occurences):-

Error Type 3(Approx 13 occurences):-

Compiling /root/swift-source/lldb/packages/Python/lldbsuite/test/lang/swift/archetype_resolution_subclass/main.swift

Merging swift modules for a

Wrapping swift module

Linking a.out

FAIL: test_dwarf (lldbsuite.test.lldbtest.TestArchetypeResolutionSubclass)

Many of the remaining test cases throw up errors like below:-
Error Type 1(Approx 49 occurences):-