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-1351] Add a way to run swift-test on a fixture in tests #5453

Open
swift-ci opened this issue Apr 28, 2016 · 2 comments
Open

[SR-1351] Add a way to run swift-test on a fixture in tests #5453

swift-ci opened this issue Apr 28, 2016 · 2 comments
Assignees
Labels

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-1351
Radar None
Original Reporter czechboy0 (JIRA User)
Type Bug
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug
Assignee @ddunbar
Priority Medium

md5: 725492ca9c4d45e17807b793a4cfc46f

Issue Description:

Currently SwiftPM tests can verify that a fixture can build in SwiftPM, but no that it can test. To avoid swift-test specific bugs for certain layouts, we should add a way to run swift-test on a fixture. See discussion here: #282 (comment)

@ddunbar
Copy link
Member

ddunbar commented May 20, 2016

See:
#143 (comment)
for more context.

@ddunbar
Copy link
Member

ddunbar commented May 27, 2016

I started looking at this again last night.

I was hoping that we could extend the "fake toolchain" concept we use in the bootstrap script to just also support Foundation and XCTest. However, it turns out this doesn't work. The problem is that the Swift compiler will find its resources relative to the realpath of itself, and so it wants to find them in the swift build directory.

At the same time, I am investigating: https://bugs.swift.org/browse/SR-1631 which is annoying because I need to investigate with a built toolchain which the normal development process doesn't have.

The combination of the two of these is making me want to push more on my "toolchain based build process" ideas...

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

No branches or pull requests

3 participants