The swift-ci tests have been regularly failing for the past several days. That makes it impossible to make progress for anyone who is trying to gate their own changes on pull request testing or even rely on local testing on trunk.
I thunk swift-ci would work if everyone followed some minimal standards for pre-commit testing: - To commit anything nontrivial, use a pull request with @swift-ci Please smoke test and merge - If your change is source breaking or may require updates in other repositories, run "utils/build-toolchain local.swift” on linux and darwin. All tests should pass and it should generate a tarball. Then use a pull request and merge all affected repositories at once. - Watch the bots after you merge. Revert your change if anything breaks. Andy Current swift-ci incremental status: > linux: > > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/6593/consoleFull#-1843642957ee1a197b-acac-4b17-83cf-a53b95139a76 > > TestFoundation/TestNSString.swift:1094:56: error: incorrect argument label in > call (have 'with:isEquivalent:', expected 'with:by:') > let expectHasPrefix = lhsNFDGraphemeClusters.starts( > ^ > TestFoundation/TestNSString.swift:1097:54: error: incorrect argument label in > call (have 'with:isEquivalent:', expected 'with:by:') > lhsNFDGraphemeClusters.lazy.reversed().starts( > ^ > --- > darwin: > > https://ci.swift.org/job/oss-swift-incremental-RA-osx/5294/consoleFull#-115900982ee1a197b-acac-4b17-83cf-a53b95139a76 > > /Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swift/stdlib/private/StdlibUnittestFoundationExtras/StdlibUnittestFoundationExtras.swift:71:19: > error: missing argument label 'invoking:' in call > autoreleasepool(body) > ^ > invoking: > _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
