Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-3273] 1 test unexpected failure on Linux From Scratch (LFS) #45861

Open
swift-ci opened this issue Nov 26, 2016 · 7 comments
Open

[SR-3273] 1 test unexpected failure on Linux From Scratch (LFS) #45861

swift-ci opened this issue Nov 26, 2016 · 7 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler itself Linux Platform: Linux runtime The Swift Runtime

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-3273
Radar None
Original Reporter Vladislav (JIRA User)
Type Bug
Environment

Linux hp-ved-lfs 4.8.10 #1 SMP Mon Nov 21 18:53:41 MSK 2016 x86_64 GNU/Linux

clang version 3.9.0 (tags/RELEASE_390/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix

python --version
Python 2.7.12

python3 --version
Python 3.5.2

ld.gold --version
GNU gold (GNU Binutils 2.27) 1.12

Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug, Linux, Runtime
Assignee None
Priority Medium

md5: c7fba57aaaf4e0312b2fdfd60d1ae644

relates to:

  • SR-3274 Failed to launch REPL process on LFS

Issue Description:

Today I have cloned new git files and tried to install SWIFT on LFS.
During test phase I have got the following results:

********************
Failing Tests (1):
Swift(linux-x86_64) :: Runtime/linux-fatal-backtrace.swift

Expected Passes : 7950
Expected Failures : 71
Unsupported Tests : 878
Unexpected Failures: 1

      • Failed while running tests for swift (check-swift-all-linux-x86_64)

The same error I got on Gentoo. Please, see https://bugs.swift.org/browse/SR-2966
But LFS uses more recent build tools versions. Does it mean that the bug is a Swift internal?

@swift-ci
Copy link
Contributor Author

swift-ci commented Feb 9, 2017

Comment by Vladislav Dembskiy (JIRA)

With latest checkout the same error still exists

@swift-ci
Copy link
Contributor Author

Comment by Vladislav Dembskiy (JIRA)

With latest swift checkout the same test failure.
swift --version
Swift version 3.1-dev (LLVM 6aad022362, Clang 61cb7f096c, Swift f76790e)
Target: x86_64-unknown-linux-gnu

@swift-ci
Copy link
Contributor Author

Comment by Vladislav Dembskiy (JIRA)

With latest swift checkout I have got the same test failure.
$ swift --version
Swift version 3.1-dev (LLVM 2ff356406e, Clang d320eeadcb, Swift bea1f5d)
Target: x86_64-unknown-linux-gnu

$ swift
error: failed to launch REPL process: process exited with status -1 (debugserver died with signal SIGSEGV)

Mar 17 20:45:51 ved-hp-lfs7 systemd-coredump[15433]: Process 15425 (lldb-server) of user 1000 dumped core.

Stack trace of thread 15425:
#0 0x00000000006da8a5 _ZN12lldb_private13process_linux33NativeRegisterContextLinux_x86_64C2ERKNS_8ArchSpecERNS_20NativeThreadProtocolEj (lldb-server-4.0.0)
#1 0x00000000006da78e _ZN12lldb_private13process_linux26NativeRegisterContextLinux36CreateHostNativeRegisterContextLinuxERKNS_8ArchSpecERNS_20NativeThreadProtocolEj (lldb-server-4.0.0)
#2 0x00000000006d8d25 _ZN12lldb_private13process_linux17NativeThreadLinux18GetRegisterContextEv (lldb-server-4.0.0)
#3 0x000000000058234f _ZL18GetJSONThreadsInfoRN12lldb_private21NativeProcessProtocolEb (lldb-server-4.0.0)
#4 0x00000000005817a1 _ZN12lldb_private18process_gdb_remote32GDBRemoteCommunicationServerLLGS28SendStopReplyPacketForThreadEm (lldb-server-4.0.0)
#5 0x00000000005855a1 ZNSt17_Function_handlerIFN12lldb_private18process_gdb_remote22GDBRemoteCommunication12PacketResultER24StringExtractorGDBRemoteRNS0_5ErrorERbS8_EZNS1_34GDBRemoteCommunicationServerCommon29RegisterMemberFunctionHandlerINS1_32GDBRemoteCommunicationServerLLGSEEEvNS4_16ServerPacketTypeEMT_FS3_S5_EEUlS4_S7_S8_S8_E_E9_M_invokeERKSt9_Any_dataS5_S7_S8_S8 (lldb-server-4.0.0)
#6 0x000000000057526b ZN12lldb_private18process_gdb_remote28GDBRemoteCommunicationServer24GetPacketAndSendResponseENS_7TimeoutISt5ratioILl1ELl1000000EEEERNS_5ErrorERbS8 (lldb-server-4.0.0)
#7 0x0000000000584302 _ZN12lldb_private18process_gdb_remote32GDBRemoteCommunicationServerLLGS21DataAvailableCallbackEv (lldb-server-4.0.0)
#8 0x0000000000529a3f _ZN12lldb_private13MainLoopPosix3RunEv (lldb-server-4.0.0)
#9 0x0000000000438c86 _Z14main_gdbserveriPPc (lldb-server-4.0.0)
#10 0x000000000043ac2a main (lldb-server-4.0.0)
#11 0x00007f1d14e6de5c __libc_start_main (libc.so.6)
#12 0x0000000000436c5a _start (lldb-server-4.0.0)

@swift-ci
Copy link
Contributor Author

swift-ci commented May 8, 2017

Comment by Vladislav Dembskiy (JIRA)

REPL is working now but backtraice test still fail.

Testing Time: 8391.86s
********************
Failing Tests (1):
Swift(linux-x86_64) :: Runtime/linux-fatal-backtrace.swift

Expected Passes : 8831
Expected Failures : 88
Unsupported Tests : 882
Unexpected Failures: 1

2 warning(s) in tests.

Failed while running tests for swift (check-swift-all-linux-x86_64)

Swift version 4.0-dev (LLVM 3df4892fbe, Clang 1a30829a18, Swift 8d888b5)
Target: x86_64-unknown-linux-gnu

@swift-ci
Copy link
Contributor Author

Comment by Vladislav Dembskiy (JIRA)

After fresh checkout I have got another failing test:
Failing Tests (1):
Swift(linux-x86_64) :: Constraints/tuple_arguments.swift

Expected Passes : 8931
Expected Failures : 85
Unsupported Tests : 910
Unexpected Failures: 1

2 warning(s) in tests.
Failed while running tests for swift (check-swift-all-linux-x86_64)

@swift-ci
Copy link
Contributor Author

swift-ci commented Aug 3, 2017

Comment by Vladislav Dembskiy (JIRA)

I did fresh checkout and got an old error:
Failing Tests (1):
Swift(linux-x86_64) :: Runtime/linux-fatal-backtrace.swift

Expected Passes : 9117
Expected Failures : 95
Unsupported Tests : 948
Unexpected Failures: 1

2 warning(s) in tests.
Failed while running tests for swift (check-swift-all-linux-x86_64)

@swift-ci
Copy link
Contributor Author

Comment by Vladislav Dembskiy (JIRA)

After fresh checkout I have got new pkgconfig test error:

Test Suite 'PkgConfigTests' started at 2017-08-10 05:34:31.845
Test Case 'PkgConfigTests.testBasics' started at 2017-08-10 05:34:31.845
/mnt/swift/swift-source/swiftpm/Tests/PackageLoadingTests/PkgConfigTests.swift:59: error: PkgConfigTests.testBasics : failed - Expected a provider here
Test Case 'PkgConfigTests.testBasics' failed (0.011 seconds)
Test Suite 'PkgConfigTests' failed at 2017-08-10 05:34:31.856
Executed 1 test, with 1 failure (0 unexpected) in 0.011 (0.011) seconds
Test Suite 'Selected tests' failed at 2017-08-10 05:34:31.856
Executed 1 test, with 1 failure (0 unexpected) in 0.011 (0.011) seconds-– bootstrap: error: tests failed with exit status 1
utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler itself Linux Platform: Linux runtime The Swift Runtime
Projects
None yet
Development

No branches or pull requests

1 participant