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
The darwin/arm and darwin/arm64 builds are very slow and currently only run one at a time for stability. Most of the time, at least in the weekdays when the Go tree is open, the builds don't catch up to the latest commit. That means that detection of potential build breakage will show up later than necessary. I wonder if it would be possible (and desirable) to always select the latest git revision when starting a build. At least for the very slow iOS builder. Today the builder will often select a build that is not even on the first page of build.golang.org.
The text was updated successfully, but these errors were encountered:
The darwin/arm and darwin/arm64 builds are very slow and currently only run one at a time for stability. Most of the time, at least in the weekdays when the Go tree is open, the builds don't catch up to the latest commit. That means that detection of potential build breakage will show up later than necessary. I wonder if it would be possible (and desirable) to always select the latest git revision when starting a build. At least for the very slow iOS builder. Today the builder will often select a build that is not even on the first page of build.golang.org.
The text was updated successfully, but these errors were encountered: