There haven't been any new trunk development (main) snapshots published at Swift.org - Download Swift for two weeks now. When can we expect new builds?
cc @mishal_shah
There haven't been any new trunk development (main) snapshots published at Swift.org - Download Swift for two weeks now. When can we expect new builds?
cc @mishal_shah
Development snapshots are tagged nightly on a condition that toolchain tests are passing on all platforms, which may not always be the case. For a new snapshot to be created again all of the failing toolchain tests have to be fixed on all officially supported platforms.
I see, thank you for explaining the reason!
A trunk snapshot was just tagged, along with one from the 6.0 branch.
Looks like this has happened again, ie no trunk snapshots tagged for the last month, no 6.2 snapshots for the last two weeks.
@mishal_shah, is there any way for the community to pitch in to having these snapshots tagged more often, especially since some of us run our CI with them? If nothing else, some public visibility into the particular issues causing snapshots not to be tagged on any given day might be informative, even if nobody ends up contributing to actually fixing them.
The CI jobs are executed on ci.swift.org and ci-external.swift.org. Before the backend infrastructure pushes the changes to swift.org, it ensures that all platforms are passing the tests. Only then does it tag and publish the changes on swift.org.
You can find the full list of jobs in swiftlang/swift README.md
Thanks for explaining how it works, as I didn't know if there are other CI, like the Swift source compatibility suite, which these official snapshots are gated on. I'm currently getting the Android CI green again, I'll keep an eye on the linux CI too. I notice that none of the Windows CI you linked were run between April 30 and May 8, so maybe that was part of the problem.
Are there different rules when the Static Linux SDK snapshots are supposed to be built? The latest trunk build is from 1st of January. Also it is not listed in the Cross-Compilation Targets
targets section of the readme.
Yes, Swift SDK for statically linked Musl by definition is not a toolchain, hence it's not a part of toolchain packaging jobs, and isn't required to be tagged synchronously with development toolchains. There's a separate job for it that maybe @al45tair could point to.
The nightly job is here: Swift Build Fully static SDK for Swift (nightly) [Jenkins]
Note that it hasn't been building for a while now (I have a few patches queued up to fix that).