Local unit test failures

Brian_King · March 12, 2017, 12:59pm

Hey Folks,
I'm a bit stumped with some unit test failures that only occur on my
machine, and was hoping someone had some clues. They occur with fresh
checkouts of all of the repositories, and I'm running the latest Xcode beta
on 10.12.3. Swift builds fine, but when I run the tests with the default
`utils/build-script --test`, there are a bunch of failures with the tests
explicitly unwrapping and crashing, as well as a few crashes calling
_swift_release_dealloc from inside of `===`.

Any idea what the problem could be? I'm not sure how I could break
something so specific without any local changes.

Here's some log output:

gist.github.com

https://gist.github.com/KingOfBrian/ea74d12015a58b05ab1f130f88ac144b

0_Failure_Backtrace

(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT)
  * frame #0: 0x000000010051d687 libswiftCore.dylib`::_swift_release_dealloc(object=0x0000000101509670) at HeapObject.cpp:558
    frame #1: 0x0000000100528166 libswiftCore.dylib`bool swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1> >::doDecrementSlow<(this=0x0000000101509678, oldbits=(bits = 0), dec=1)0, (swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) at RefCount.h:1046
    frame #2: 0x0000000100526b8c libswiftCore.dylib`bool swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1> >::doDecrement<(this=0x0000000101509678, dec=1)0, (swift::PerformDeinit)1>(unsigned int) at RefCount.h:1104
    frame #3: 0x0000000100517381 libswiftCore.dylib`::_swift_release_(swift::HeapObject *) [inlined] swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1> >::decrementAndMaybeDeinit(this=0x0000000101509678, dec=1) at RefCount.h:907
    frame #4: 0x0000000100517379 libswiftCore.dylib`::_swift_release_(object=0x0000000101509670) at HeapObject.cpp:280
    frame #5: 0x000000010015fa26 libswiftCore.dylib`=== infix(lhs=(instance_type = 0x0000000101509670), rhs=(instance_type = 0x0000000101509670)) -> Bool at Equatable.swift:238
    frame #6: 0x0000000100002607 main`main.sameObject (Swift.Optional<Any>, Swift.Optional<Any>) -> Swift.Bool + 327
    frame #7: 0x0000000100002a79 main`main.(closure #1) + 617

This file has been truncated. show original

0_Test_Failures

Failing Tests (22):
    Swift(macosx-x86_64) :: stdlib/Reflection_objc.swift
    Swift(macosx-x86_64) :: stdlib/NSDictionary.swift
    Swift(macosx-x86_64) :: Interpreter/SDK/objc_extensions.swift
    Swift(macosx-x86_64) :: Interpreter/SDK/objc_switch.swift
    Swift(macosx-x86_64) :: Interpreter/imported_objc_generics.swift
    Swift(macosx-x86_64) :: Interpreter/SDK/KVO.swift
    Swift(macosx-x86_64) :: Interpreter/SDK/objc_array_of_classes.swift
    Swift(macosx-x86_64) :: stdlib/NSObject.swift
    Swift(macosx-x86_64) :: stdlib/OptionalBridge.swift

This file has been truncated. show original

1_Lit_Output

--- check-swift-macosx-x86_64 ---
Generating dry run test command from: /usr/local/bin/cmake --build /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64 -- -j8 -n -v check-swift-macosx-x86_64
Test command: cd /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/test && /usr/local/Cellar/cmake/3.7.2/bin/cmake -E remove_directory /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/./swift-test-results/x86_64-apple-macosx10.9 && /usr/local/Cellar/cmake/3.7.2/bin/cmake -E make_directory /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/./swift-test-results/x86_64-apple-macosx10.9 && /usr/bin/python /Users/bking/sandbox/swift-source/llvm/utils/lit/lit.py --incremental -sv --xunit-xml-output=/Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/./swift-test-results/x86_64-apple-macosx10.9/lit-tests.xml --param swift_test_subset=primary --param swift_test_mode=optimize_none /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64
+ cd /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/test
+ /usr/local/Cellar/cmake/3.7.2/bin/cmake -E remove_directory /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/./swift-test-results/x86_64-apple-macosx10.9
+ /usr/local/Cellar/cmake/3.7.2/bin/cmake -E make_directory /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/./swift-test-results/x86_64-apple-macosx10.9
+ /usr/bin/python /Users/bking/sandbox/swift-source/llvm/utils/lit/lit.py --incremental -sv --xunit-xml-output=/Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/./swift-test-results/x86_64-apple-macosx10.9/lit-tests.xml --param swift_test_subset=primary --param swift_test_mode=optimize_none /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64
lit.py: /Users/bking/sandbox/swift-source/swift/test/lit.cfg:256: note: using swift: /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/bin/swift
lit.py: /Users/bking/sandbox/swift-source/swift/test/lit.cfg:256: note: using swiftc: /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/bin/swiftc
lit.py: /Users/bking/sandbox/swift-source/swift/test/lit.cfg:256: note: using sil-opt: /Users/bking/sandbox/swift-source/build/Ninja-DebugAssert/swift-macosx-x86_64/bin/sil-opt

This file has been truncated. show original

Any help would be great. Not being able to trust my unit tests locally has
been a bit un-nerving!

Brian King

Michael_Gottesman · March 12, 2017, 5:52pm

There is some breakage right now on the debug assert build. I think that is what you are hitting.

You can see this here:

https://ci.swift.org/job/oss-swift_tools-RA_stdlib-DA_test-simulator

If it is the same test failures as you are seeing, I would assume that is the issue.

Michael

···

On Mar 12, 2017, at 5:59 AM, Brian King via swift-dev <swift-dev@swift.org> wrote:

Hey Folks,
I'm a bit stumped with some unit test failures that only occur on my machine, and was hoping someone had some clues. They occur with fresh checkouts of all of the repositories, and I'm running the latest Xcode beta on 10.12.3. Swift builds fine, but when I run the tests with the default `utils/build-script --test`, there are a bunch of failures with the tests explicitly unwrapping and crashing, as well as a few crashes calling _swift_release_dealloc from inside of `===`.

Any idea what the problem could be? I'm not sure how I could break something so specific without any local changes.

Here's some log output:
Test Failures · GitHub
Any help would be great. Not being able to trust my unit tests locally has been a bit un-nerving!

Brian King

_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Brian_King · March 13, 2017, 7:42pm

Great, thanks Michael, looks like that's the issue -- I'll check there in
the future

···

On Sun, Mar 12, 2017 at 1:52 PM, Michael Gottesman <mgottesman@apple.com> wrote:

There is some breakage right now on the debug assert build. I think that
is what you are hitting.

You can see this here:

https://ci.swift.org/job/oss-swift_tools-RA_stdlib-DA_test-simulator

If it is the same test failures as you are seeing, I would assume that is
the issue.

Michael

On Mar 12, 2017, at 5:59 AM, Brian King via swift-dev <swift-dev@swift.org> > wrote:

Hey Folks,
I'm a bit stumped with some unit test failures that only occur on my
machine, and was hoping someone had some clues. They occur with fresh
checkouts of all of the repositories, and I'm running the latest Xcode beta
on 10.12.3. Swift builds fine, but when I run the tests with the default
`utils/build-script --test`, there are a bunch of failures with the tests
explicitly unwrapping and crashing, as well as a few crashes calling
_swift_release_dealloc from inside of `===`.

Any idea what the problem could be? I'm not sure how I could break
something so specific without any local changes.

Here's some log output:
Test Failures · GitHub

Any help would be great. Not being able to trust my unit tests locally has
been a bit un-nerving!

Brian King
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev