Swift-corelibs-foundation testing is broken

Here:

https://ci.swift.org/view/Pull%20Request/job/swift-corelibs-foundation-PR-Linux/766/consoleFull#-20750154173122a513-f36a-4c87-8ed7-cbc36a1ec144

Or here:

https://ci.swift.org/view/Pull%20Request/job/swift-corelibs-foundation-PR-Linux/760/consoleFull#-20750154173122a513-f36a-4c87-8ed7-cbc36a1ec144

19:29:06 --- bootstrap: note: building self-hosted 'swift-build': env SWIFT_EXEC=/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swiftc SWIFTPM_BUILD_DIR=/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/swiftpm-linux-x86_64 /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swift-build-stage1 --disable-sandbox -Xlinker -rpath -Xlinker $ORIGIN/../lib/swift/linux -Xlinker -L -Xlinker /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation -Xlinker -rpath -Xlinker /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation/usr/lib/swift -Xlinker -L -Xlinker /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/xctest-linux-x86_64 -Xlinker -rpath -Xlinker /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/xctest-linux-x86_64 -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/xctest-linux-x86_64 -Xlinker -L/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/libdispatch-linux-x86_64/src/.libs -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/libdispatch-linux-x86_64/src -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/libdispatch-linux-x86_64/src/swift -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/swift-corelibs-libdispatch -Xcc -fblocks -Xswiftc -enable-testing --configuration release --build-tests
19:29:08 --- bootstrap: note: testing with command: env SWIFT_EXEC=/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swiftc SWIFTPM_BUILD_DIR=/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/swiftpm-linux-x86_64 /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swift-test --disable-sandbox -Xlinker -rpath -Xlinker $ORIGIN/../lib/swift/linux -Xlinker -L -Xlinker /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation -Xlinker -rpath -Xlinker /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation/usr/lib/swift -Xlinker -L -Xlinker /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/xctest-linux-x86_64 -Xlinker -rpath -Xlinker /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/xctest-linux-x86_64 -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/xctest-linux-x86_64 -Xlinker -L/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/libdispatch-linux-x86_64/src/.libs -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/libdispatch-linux-x86_64/src -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/libdispatch-linux-x86_64/src/swift -Xswiftc -I/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/swift-corelibs-libdispatch -Xcc -fblocks -Xswiftc -enable-testing --configuration release --parallel
19:29:08 /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux@2/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swift-test: error while loading shared libraries: libswiftSwiftOnoneSupport.so: cannot open shared object file: No such file or directory

Hmm that work surpisingly bad.

x86_64-unknown-linux/release/swift-test: error while loading shared libraries: libswiftSwiftOnoneSupport.so: cannot open shared object file: No such file or directory

CC @Erik_Eckstein

@Ankit_Agarwal Could this be due to a swiftpm change? Or a build-script change?

Most likely build-script. There is no recent commit in SwiftPM that can cause this.

The last successful run of the bot AFAICT was running with different build-script options

Successful run https://ci.swift.org/view/Pull%20Request/job/swift-corelibs-foundation-PR-Linux/758

+ /home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux/swift/utils/build-script -R -T --llbuild --swiftpm --xctest --foundation --libdispatch -- --reconfigure --lit-args=-v

The bot now runs with the following options (first bot run with the same failure https://ci.swift.org/view/Pull%20Request/job/swift-corelibs-foundation-PR-Linux/760). Note that we now use ---debug-foundation:

./utils/build-script -R -T --llbuild --swiftpm --xctest --debug-foundation --libdispatch -- --reconfigure --lit-args=-v

@mishal_shah or @Erik_Eckstein Do you know what is going on here? PR testing and merging in Foundation is blocked because of that!

I have filed https://bugs.swift.org/browse/SR-7154

The only thing that changed is that Foundation is building debug (so we can enable @testable import), and looks like this is changing the linkages in a way whatever is building SwiftPM doesn’t expect.

Please revert the change that caused this and re-land with the corresponding update in SwiftPM’s bootstrap script. If you need help with the SwiftPM change, please file a bug with instruction on how to reproduce. But in the meantime I suggest reverting the change to unblock people.

https://bugs.swift.org/browse/SR-7154 now has the instructions how to reproduce it

I have asked @mishal_shah to change the build bot configuration back to:

./utils/build-script -R -T --llbuild --swiftpm --xctest --foundation --libdispatch – --reconfigure --lit-args=-v

1 Like

To unblock PR testing, I reverted the --debug-foundation flag until we have SwiftPM change.

Thank you!