Running on ubuntu-latest fails when linking for tests

[beatt83]

Hey there.

I was using this to enable Android on my library, but while building with the GitHub action it would always fail with the following errors (below).
After some experimenting I discovered that this issue just happens when running on ubuntu-latest, it does not happen with macos-13 or macos-15 (yes I know this last will not run the tests :) ) in macos runners it will succeed building and start the emulator (or try to start the emulator) to run the tests.

It seems the issue is with swift-crypto, I dont know if its useful but my library runs and tests on linux without a problem.

[984/1006] Write Objects.LinkFileList
error: link command failed with exit code 1 (use -v to see invocation)
ld.lld: error: undefined symbol: __assert2
>>> referenced by pkcs8.cc:211 (.build/checkouts/swift-crypto/Sources/CCryptoBoringSSL/crypto/pkcs8/pkcs8.cc:211)
>>>               /home/runner/work/jose-swift/jose-swift/.build/x86_64-unknown-linux-android24/debug/CCryptoBoringSSL.build/crypto/pkcs8/pkcs8.cc.o:(CCryptoBoringSSL_pkcs12_key_gen)
>>> referenced by x_x509.cc:442 (.build/checkouts/swift-crypto/Sources/CCryptoBoringSSL/crypto/x509/x_x509.cc:442)
>>>               /home/runner/work/jose-swift/jose-swift/.build/x86_64-unknown-linux-android24/debug/CCryptoBoringSSL.build/crypto/x509/x_x509.cc.o:(i2d_x509_aux_internal(x509_st*, unsigned char**))
>>> referenced by x_crl.cc:348 (.build/checkouts/swift-crypto/Sources/CCryptoBoringSSL/crypto/x509/x_crl.cc:348)
>>>               /home/runner/work/jose-swift/jose-swift/.build/x86_64-unknown-linux-android24/debug/CCryptoBoringSSL.build/crypto/x509/x_crl.cc.o:(crl_lookup(X509_crl_st*, x509_revoked_st**, asn1_string_st const*, X509_name_st*))
>>> referenced 512 more times
>>> did you mean: __assert
>>> defined in: /lib/x86_64-linux-gnu/libc.so.6
ld.lld: error: undefined symbol: __errno
>>> referenced by urandom.cc:149 (.build/checkouts/swift-crypto/Sources/CCryptoBoringSSL/crypto/rand_extra/urandom.cc:149)
>>>               /home/runner/work/jose-swift/jose-swift/.build/x86_64-unknown-linux-android24/debug/CCryptoBoringSSL.build/crypto/rand_extra/urandom.cc.o:(init_once())
>>> referenced by urandom.cc:152 (.build/checkouts/swift-crypto/Sources/CCryptoBoringSSL/crypto/rand_extra/urandom.cc:152)
>>>               /home/runner/work/jose-swift/jose-swift/.build/x86_64-unknown-linux-android24/debug/CCryptoBoringSSL.build/crypto/rand_extra/urandom.cc.o:(init_once())
>>> referenced by urandom.cc:183 (.build/checkouts/swift-crypto/Sources/CCryptoBoringSSL/crypto/rand_extra/urandom.cc:183)
>>>               /home/runner/work/jose-swift/jose-swift/.build/x86_64-unknown-linux-android24/debug/CCryptoBoringSSL.build/crypto/rand_extra/urandom.cc.o:(init_once())
>>> referenced 16 more times
ld.lld: error: undefined symbol: __sF
>>> referenced by UnwindLevel1.c
>>>               UnwindLevel1.c.o:(unwind_phase2) in archive /home/runner/.config/swiftpm/swift-sdks/swift-6.1-RELEASE-android-24-0.1.artifactbundle/swift-6.1-release-android-24-sdk/android-27c-sysroot/usr/lib/swift/clang/lib/linux/x86_64/libunwind.a
>>> referenced by UnwindLevel1.c
>>>               UnwindLevel1.c.o:(_Unwind_Resume) in archive /home/runner/.config/swiftpm/swift-sdks/swift-6.1-RELEASE-android-24-0.1.artifactbundle/swift-6.1-release-android-24-sdk/android-27c-sysroot/usr/lib/swift/clang/lib/linux/x86_64/libunwind.a
>>> referenced by libunwind.cpp
>>>               libunwind.cpp.o:(libunwind::CFI_Parser<libunwind::LocalAddressSpace>::parseCIE(libunwind::LocalAddressSpace&, unsigned long, libunwind::CFI_Parser<libunwind::LocalAddressSpace>::CIE_Info*)) in archive /home/runner/.config/swiftpm/swift-sdks/swift-6.1-RELEASE-android-24-0.1.artifactbundle/swift-6.1-release-android-24-sdk/android-27c-sysroot/usr/lib/swift/clang/lib/linux/x86_64/libunwind.a
>>> referenced 55 more times
ld.lld: error: undefined symbol: __libc_init
>>> referenced by crtbegin.c
>>>               /home/runner/.config/swiftpm/swift-sdks/swift-6.1-RELEASE-android-24-0.1.artifactbundle/swift-6.1-release-android-24-sdk/android-27c-sysroot/usr/lib/x86_64-linux-android/24/crtbegin_dynamic.o:(_start_main)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[985/1006] Linking jose-swiftPackageTests.xctest

[marcprux]

That's odd. We are building swift-crypto periodically with an action that validates various "major" packages (see https://github.com/swift-everywhere/swift-package-builds/actions/runs/14645153664/job/41097321089), but we aren't running the tests.

Is your workflow part of a public repository and something we can look at? Or is there some minimally reproducible example of this failure you could create?

[beatt83]

I cannot really identify the problem, but it seems to be the tests indeed, so you need to have run-tests enabled.

Yes my repository is public you can see the actions here:

Here is the failing job for ubuntu-latest: https://github.com/beatt83/jose-swift/actions/runs/14645237180/job/41097615077

And here is the success job for macos-13: https://github.com/beatt83/jose-swift/actions/runs/14645735247/job/41099293623

macOS-13 works fine is just very very slow.

[marcprux]

I was just able to run the swift-crypto tests (main branch) on an ubuntu-latest runner: https://github.com/swift-everywhere/swift-package-builds/actions/runs/14647724788/job/41105993485 (not all the tests fail, but that is because some resources were not being copied over)

One thing that I notice in your test run is that it is using an older version of swift-crypto (3.10.2, whereas the latest version is 3.12.3):

Computing version for https://github.com/apple/swift-crypto.git
Computed https://github.com/apple/swift-crypto.git at 3.10.2 (1.62s)

You don't appear to have a Package.resolved pinning it, so I'm guessing that one of your dependencies is specifying an exact older version of swift-crypto. I wonder if you managed to force it to use the latest version if that would address the issue? I ask because I recall there were some Android-specific fixes recently that may have fixed this particular error.

[beatt83]

Yes so I noticed I forced it while trying to make it work, so I removed the force but no change the tests still failed to build on ubuntu-latest and not on macos-13.

Here are the new tries with swift-crypto version 3.12.3.

Success (macos-13): https://github.com/beatt83/jose-swift/actions/runs/14646206879/job/41100934895
Failure (ubuntu-latest): https://github.com/beatt83/jose-swift/actions/runs/14646081777/job/41100478648

I wonder if you make some library that depends on swift-crypto and do some tests if it we can replicate the error.