[swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 - Long Test (master) #2126

[Bob Wilson]

The hope is that the “SkyNet” project that Marc Shifer’s team is developing will be able to help with things like that. The “emoji hashes” in our new Jenkins 2 bots are the first step in that direction….

> On Apr 14, 2017, at 9:08 PM, Andrew Trick <atrick at apple.com> wrote:
> 
> > runtime/SwiftRuntimeTests/MetadataTest.getExistentialMetadata’ FAILED
> 
> This is unrelated to my commit and recovered on the next build. Is it spurious? Can CI be taught to recognize known spurious asserts?
> 
> -Andy
> 
> 
>> On Apr 14, 2017, at 7:51 PM, no-reply at swift.org <mailto:no-reply at swift.org> wrote:
>> 
>> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04-long-test [#2126]
>> 
>> Build URL:	https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04-long-test/2126/ <https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04-long-test/2126/>
>> Project:	oss-swift-incremental-RA-linux-ubuntu-14_04-long-test
>> Date of build:	Fri, 14 Apr 2017 19:18:26 -0700
>> Build duration:	33 min
>> Identified problems:
>> 
>> Regression test failed: This build failed because a regression test in the test suite FAILed. Below is a list of all errors:
>> Indication 1 <https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-14_04-long-test/2126/consoleFull#-1960388827fca400bf-2f4a-462e-b517-e058d770b2d7>
>> Changes
>> 
>> Commit 915b3198107fb1f0c200e433227dcca7c9943343 by Andrew Trick:
>> [AccessEnforce] must handle `undef` before diagnostics.
>> 
>> edit: lib/SILOptimizer/Mandatory/AccessEnforcementSelection.cpp
>> edit: test/SILOptimizer/access_enforcement_selection.swift
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-dev/attachments/20170414/7c186ba9/attachment.html>