Skip to content

Tests: use RelativePath in XcodeprojTests for path references #5514

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

Closed
wants to merge 1 commit into from

Conversation

compnerd
Copy link
Member

This adjusts the test expectations to use RelativePath to construct
the path with the preferred platform path separator rather than the
hardcoded /. This enables the test suite to pass on Windows.

This adjusts the test expectations to use `RelativePath` to construct
the path with the preferred platform path separator rather than the
hardcoded `/`.  This enables the test suite to pass on Windows.
@compnerd
Copy link
Member Author

@swift-ci please test

@@ -137,7 +137,7 @@ class PackageGraphTests: XCTestCase {
XCTAssertEqual(targetResult.commonBuildSettings.OTHER_LDFLAGS?.first, "$(inherited)")
XCTAssertEqual(targetResult.commonBuildSettings.OTHER_SWIFT_FLAGS?.first, "$(inherited)")
XCTAssertEqual(targetResult.commonBuildSettings.SKIP_INSTALL, "YES")
XCTAssertEqual(targetResult.target.buildSettings.xcconfigFileRef?.path, "../Overrides.xcconfig")
XCTAssertEqual(targetResult.target.buildSettings.xcconfigFileRef?.path, RelativePath(unsafeUncheckedPath: "../Overrides.xcconfig").pathString)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

curios, why do we need to use the unsafeUncheckedPath variant?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because we cannot normalize ../Overrides.xcconfig without an anchor.

@tomerd tomerd added the windows label Jun 2, 2022
@tomerd
Copy link
Contributor

tomerd commented Apr 17, 2023

@compnerd can this be closed given #5910?

@compnerd
Copy link
Member Author

The current failures do seem to be outside of this set, so .... yeah, lets assume that this is no longer needed.

@compnerd compnerd closed this Apr 18, 2023
@compnerd compnerd deleted the relatively-complete branch April 18, 2023 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants