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

Jump to bottom

[SR-8246] Runtime/linux-fatal-backtrace.swift test failing on Linux/AArch64 #50778

Open
futurejones opened this issue Jul 13, 2018 · 3 comments
Open

[SR-8246] Runtime/linux-fatal-backtrace.swift test failing on Linux/AArch64 #50778

futurejones opened this issue Jul 13, 2018 · 3 comments
Labels
arm64 Architecture: arm64 (aarch64) — any 64-bit ARM bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself Linux Platform: Linux

Comments

@futurejones
Copy link
Contributor

Previous ID SR-8246
Radar None
Original Reporter @futurejones
Type Bug
Environment

Linux Ubuntu 16.04 LTS on AArch64
https://ci-external.swift.org/computer/ubuntu-16.04-aarch64/

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

md5: 2c6dcf190cb0c7b25d2ed2b78fa847a0

Issue Description:

Runtime/linux-fatal-backtrace.swift test is failing on swift-4.1-branch, swift-4.2-branch and the master.

Build machine - https://ci-external.swift.org/computer/ubuntu-16.04-aarch64/

Console output:

FAIL: Swift(linux-aarch64) :: Runtime/linux-fatal-backtrace.swift (9047 of 10668)
******************** TEST 'Swift(linux-aarch64) :: Runtime/linux-fatal-backtrace.swift' FAILED ********************
Script:
--
rm -rf /home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp
mkdir -p /home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp
/home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/build/buildbot_linux/swift-linux-aarch64/bin/swiftc -target aarch64-unknown-linux-gnu  -module-cache-path '/tmp/swift-testsuite-clang-module-cacheMFmh6q' -swift-version 3  /home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/swift/test/Runtime/linux-fatal-backtrace.swift -o /home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out
not --crash /home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out 2>&1 | PYTHONPATH=/home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/build/buildbot_linux/lldb-linux-aarch64/lib/python2.7/site-packages /home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/swift/utils/symbolicate-linux-fatal /home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out - | /home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/swift/utils/backtrace-check -u
--
Exit Code: 1

Command Output (stderr):
--
Traceback (most recent call last):
  File "/home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/swift/utils/backtrace-check", line 84, in <module>
    main()
  File "/home/worksonarm_test/jenkins_slave/workspace/swift-4.1-branch-aarch64-with-tests/swift/utils/backtrace-check", line 80, in main
    assert(found_stack_trace_entry)
AssertionError

--

********************
@belkadan
Copy link
Contributor

Maybe the AArch64 backtrace format is different?

@swift-ci
Copy link
Collaborator

Comment by Jason Miller (JIRA)

I don't think this is just a problem with the test failing because it's looking for the wrong thing. We actually don't get backtraces at all on AArch64. My guess is that the backtrace code is failing because the AArch64 ABI is different but that's just a guess, I haven't looked into it at all.

@futurejones
Copy link
Contributor Author

This test is still failing in Swift 5.0

******************** TEST 'Swift(linux-aarch64) :: Runtime/linux-fatal-backtrace.swift' FAILED ********************
Script:
--
: 'RUN: at line 1';   rm -rf "/home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp" && mkdir -p "/home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp"
: 'RUN: at line 2';   /home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/build/buildbot_linux/swift-linux-aarch64/bin/swiftc -target aarch64-unknown-linux-gnu  -module-cache-path '/home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/build/buildbot_linux/swift-linux-aarch64/swift-test-results/aarch64-unknown-linux-gnu/clang-module-cache' -swift-version 4   /home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/swift/test/Runtime/linux-fatal-backtrace.swift -o /home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out
: 'RUN: at line 3';   not --crash /home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out 2>&1 | PYTHONPATH=/home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/build/buildbot_linux/lldb-linux-aarch64/lib/python2.7/site-packages /home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/swift/utils/symbolicate-linux-fatal /home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/build/buildbot_linux/swift-linux-aarch64/test-linux-aarch64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out - | /home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/swift/utils/backtrace-check -u
--
Exit Code: 1

Command Output (stderr):
--
Traceback (most recent call last):
  File "/home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/swift/utils/backtrace-check", line 84, in <module>
    main()
  File "/home/worksonarm_test/jenkins_slave/workspace/swift-5.0-aarch64/swift/utils/backtrace-check", line 80, in main
    assert(found_stack_trace_entry)
AssertionError

--

********************

@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
Assignees
No one assigned
Labels
arm64 Architecture: arm64 (aarch64) — any 64-bit ARM bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself Linux Platform: Linux
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@belkadan @futurejones @swift-ci