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-2434] [XCTest] Functional tests fail to run due to stdlib versioning problem #378

Closed
briancroom opened this issue Aug 20, 2016 · 3 comments
Assignees

Comments

@briancroom
Copy link
Collaborator

Previous ID SR-2434
Radar None
Original Reporter @briancroom
Type Bug
Status Closed
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s XCTest
Labels Bug
Assignee @briancroom
Priority Medium

md5: 1d18cf777b86c9c663642f1835487a8b

Issue Description:

When run on OS X, the binaries that XCTest uses to test itself aren't loading properly, with the following error being output:

dyld: Library not loaded: @rpath/libswiftCore.dylib
  Referenced from: /Users/buildnode/jenkins/workspace/swift-corelibs-xctest-PR-osx/Ninja-DebugAssert/xctest-macosx-x86_64/Debug/SwiftXCTest.framework/Versions/A/Frameworks/libswiftDarwin.dylib
  Reason: Incompatible library version: libswiftDarwin.dylib requires version 1.0.0 or later, but libswiftCore.dylib provides version 0.0.0

The underlying cause of this is unclear to me, but it can be observed on PR CI builds starting with #83, continuing to the latest ones. #82 exhibit this problem. (Note that malfunctioning builds are still showing up as passing due to SR-2433.)

@briancroom
Copy link
Collaborator Author

The timing of this seems to coincide with CI being upgraded to use Xcode 8 beta 2, so I'm thinking an Xcode behavior change is playing a role here. From the message, I'm guessing that the Swift stdlib in Xcode is getting used alongside the just-built stdlib for some reason.

@briancroom
Copy link
Collaborator Author

PR: #168

@briancroom
Copy link
Collaborator Author

This has been fixed on master.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 9, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant