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.

Sign up for GitHub

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-7638] Test failures (including memory management count failures) occurring in Debug only on Ubuntu #50179

Open
millenomi opened this issue May 9, 2018 · 4 comments
Open

[SR-7638] Test failures (including memory management count failures) occurring in Debug only on Ubuntu #50179

millenomi opened this issue May 9, 2018 · 4 comments
Assignees
@mikeash
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. runtime The Swift Runtime standard library Area: Standard library umbrella

Comments

@millenomi
Copy link
Contributor

Previous ID SR-7638
Radar rdar://problem/40114415
Original Reporter @millenomi
Type Bug

Attachment: Download

Additional Detail from JIRA
Votes 0
Component/s Standard Library
Labels Bug, Runtime
Assignee @mikeash
Priority Medium

md5: 499ea17ccca063b75f420d6a1f7113be

Issue Description:

To reproduce, on Ubuntu 16.04:

  • Check out master (utils/update-checkout --scheme=master)

  • Run the build script as:

../swift/utils/build-script -d -t --xctest --debug-foundation --lldb

Tests will fail that do not seem to fail in Release. The failures seem legitimate, and potentially correlated to crashes I'm experiencing while trying to bring up <https://github.com/apple/swift/pull/16022\>.

See attached file for log.
@belkadan
Copy link
Contributor

belkadan commented May 9, 2018

The stats one is being flaky and was recently disabled; the linux-fatal-backtrace.swift one looks like a configuration issue. But the runtime ones seem important. @mikeash, who should this go to?

@mikeash
Copy link
Contributor

mikeash commented May 10, 2018

@swift-ci create

@mikeash
Copy link
Contributor

mikeash commented May 10, 2018

The problem is that the tests are being compiled with /usr/bin/clang++ which does not support the swiftcall attribute. The runtime is being compiled with the compiler built for Swift, which does. The mismatch causes destroyTestObject to receive garbage in its parameter. We should fix it so the tests are compiled with the compiler we built.

@mikeash
Copy link
Contributor

mikeash commented May 11, 2018

PR to fix this is here: #16508

@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

@mikeash mikeash

Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. runtime The Swift Runtime standard library Area: Standard library umbrella
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@millenomi @mikeash @belkadan