[Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.04 - Long Test (master) #6470

Development CI Notifications
1

# [FAILURE] oss-swift-incremental-RA-linux-ubuntu-16_04-long-test [#6470]

Build URL: https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_04-long-test/6470/
Project: oss-swift-incremental-RA-linux-ubuntu-16_04-long-test
Date of build: Wed, 22 Jul 2020 00:19:00 -0500
Build duration: 1 hr 11 min

Identified problems:- Compile Error: This build failed because of a compile error. Below is a list of all errors in the build log:

Changes- Commit 5091aee6f2013f26c2ff84d369bfccf43d351427 by atrick:

Add an AccessedStorageDumper pass to verify findAccessedStorage.

  • edit: lib/SIL/Utils/MemAccessUtils.cpp

  • edit: test/SILOptimizer/accessed_storage_analysis.sil

  • add: test/SILOptimizer/accessed_storage.sil

  • edit: lib/SILOptimizer/UtilityPasses/CMakeLists.txt

  • edit: include/swift/SILOptimizer/PassManager/Passes.def

  • add: lib/SILOptimizer/UtilityPasses/AccessedStorageAnalysisDumper.cpp

  • edit: lib/SILOptimizer/UtilityPasses/AccessedStorageDumper.cpp

  • Commit 6ecbeefd5024efb7834ed1608f25dcece4ed63b6 by atrick:

    Add AccessedStorage::Tail access kind and remove more checks.

    • edit: include/swift/SIL/MemAccessUtils.h
    • edit: lib/SILOptimizer/Transforms/AccessEnforcementOpts.cpp
    • edit: lib/SILOptimizer/Analysis/AccessedStorageAnalysis.cpp
    • edit: lib/SIL/Verifier/LoadBorrowInvalidationChecker.cpp
    • edit: test/SILOptimizer/accessed_storage.sil
    • edit: lib/SIL/Utils/MemAccessUtils.cpp
    • edit: test/SILOptimizer/optimize_keypath.swift
    • edit: lib/SILOptimizer/Transforms/AccessEnforcementWMO.cpp

  • Commit 7e5d566180b448962dede196eebf8b6abfa40e80 by spestov:

    GSB: An anchor cannot have a concrete parent type

    • edit: lib/AST/GenericSignatureBuilder.cpp
2

FunctionalTests/DependencyResolutionTests.swift:63: error: DependencyResolutionTests.testExternalComplex : failed - `swift build -c Release' failed:

My change shouldn’t have affected anything except possibly causing a compiler assertion. Is there any way to know what the actual error is?
-Andy