You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Re-enable disabled tests
* Re-enable disabled tests
This re-enables a bunch of disabled tests, the hope is that they should now work that we have a newer superior Xcode installed on CI. If that happens to not be the case, we have `SWIFTCI_DISABLE_SDK_DEPENDENT_TESTS` to disable these tests specifically for the macOS CI if needed. This change introduces the variable where expected to be needed, but doesn't set it.
* Removed back deployment rpaths
* Removed more Darwin rpaths into the toolchain
A macOS that contains the dyld issue worked around by swiftlang/swift#37978 has been deployed by Swift CI, so we can't do this anymore on Darwin.
* Do not include Swift runtime libs in `DYLD_LIBRARY_PATH` on Darwin
(cherry picked from commit 16fb1d2)
* Skip SDK dependent tests in macOS bootstrap
This is manifesting itself as `cannot find 'XCTAssertEqual' in scope` on Swift CI again, but instead of disabling these tests wholesale like we did before, we want to take a more targetted approach.
(cherry picked from commit bc35b9c)
* Put `CommandsTests` behind `SWIFTCI_DISABLE_SDK_DEPENDENT_TESTS`
Looks like these tests are suffering from some of the same problems as `FunctionalTests` which makes sense since they're conceptually very similar.
(cherry picked from commit 2cb0f2f)
Copy file name to clipboardExpand all lines: Package.swift
+50-37Lines changed: 50 additions & 37 deletions
Original file line number
Diff line number
Diff line change
@@ -579,47 +579,10 @@ let package = Package(
579
579
name:"BuildTests",
580
580
dependencies:["Build","SPMTestSupport"]
581
581
),
582
-
.testTarget(
583
-
name:"CommandsTests",
584
-
dependencies:[
585
-
"swift-build",
586
-
"swift-package",
587
-
"swift-test",
588
-
"swift-run",
589
-
"Basics",
590
-
"Build",
591
-
"Commands",
592
-
"PackageModel",
593
-
"PackageRegistryTool",
594
-
"SourceControl",
595
-
"SPMTestSupport",
596
-
"Workspace",
597
-
]
598
-
),
599
582
.testTarget(
600
583
name:"WorkspaceTests",
601
584
dependencies:["Workspace","SPMTestSupport"]
602
585
),
603
-
// rdar://101868275 "error: cannot find 'XCTAssertEqual' in scope" can affect almost any functional test, so we flat out disable them all until we know what is going on
604
-
/*.testTarget(
605
-
name: "FunctionalTests",
606
-
dependencies: [
607
-
"swift-build",
608
-
"swift-package",
609
-
"swift-test",
610
-
"PackageModel",
611
-
"SPMTestSupport"
612
-
]
613
-
),*/
614
-
.testTarget(
615
-
name:"FunctionalPerformanceTests",
616
-
dependencies:[
617
-
"swift-build",
618
-
"swift-package",
619
-
"swift-test",
620
-
"SPMTestSupport"
621
-
]
622
-
),
623
586
.testTarget(
624
587
name:"PackageDescriptionTests",
625
588
dependencies:["PackageDescription"]
@@ -703,6 +666,56 @@ let package = Package(
703
666
swiftLanguageVersions:[.v5]
704
667
)
705
668
669
+
// Workaround SPM's attempt to link in executables which does not work on all
670
+
// platforms.
671
+
#if !os(Windows)
672
+
package.targets.append(contentsOf:[
673
+
.testTarget(
674
+
name:"FunctionalPerformanceTests",
675
+
dependencies:[
676
+
"swift-build",
677
+
"swift-package",
678
+
"swift-test",
679
+
"SPMTestSupport"
680
+
]
681
+
),
682
+
])
683
+
684
+
// rdar://101868275 "error: cannot find 'XCTAssertEqual' in scope" can affect almost any functional test, so we flat out disable them all until we know what is going on
0 commit comments