The FreeBSD CI job is timing out at the 6-hour limit on recent PRs (#282, #284, #285). The build completes in ~60s, so the hang is in the test suite, not compilation. The suite runs in parallel, so the timeout lands in a different test on each run.
The hanging runs are on Swift version 6.3-dev (LLVM 972b62858355d07, Swift 3f8c798cfe25bbb).
#277 switched from swift_package_test.yml@0.0.11 to @main to fix issues on Android, but I don't think this was the cause, since the freebsd-build job in swift_package_test.yml is unchanged between 0.0.11 and main (only diffs are for Android/Wasm). It installs the toolchain from https://download.swift.org/tmp-ci-nightly/development/freebsd-14_ci_latest.tar.gz and accepts only nightly-main, which might have a regression.
The FreeBSD step there might also benefit from a timeout-minutes like other steps.
cc @iCharlesHu @jakepetroules
The FreeBSD CI job is timing out at the 6-hour limit on recent PRs (#282, #284, #285). The build completes in ~60s, so the hang is in the test suite, not compilation. The suite runs in parallel, so the timeout lands in a different test on each run.
The hanging runs are on
Swift version 6.3-dev (LLVM 972b62858355d07, Swift 3f8c798cfe25bbb).#277 switched from
swift_package_test.yml@0.0.11to@mainto fix issues on Android, but I don't think this was the cause, since thefreebsd-buildjob inswift_package_test.ymlis unchanged between0.0.11andmain(only diffs are for Android/Wasm). It installs the toolchain fromhttps://download.swift.org/tmp-ci-nightly/development/freebsd-14_ci_latest.tar.gzand accepts onlynightly-main, which might have a regression.The FreeBSD step there might also benefit from a
timeout-minuteslike other steps.cc @iCharlesHu @jakepetroules