Title: Report
[FAILURE] oss-swift-package-osx [#451]
Build URL:https://ci.swift.org/job/oss-swift-package-osx/451/
Project:oss-swift-package-osx
Date of build:Mon, 09 Oct 2017 04:59:55 -0500
Build duration:1 hr 35 min
Identified problems:Regression test failed: This build
New issue found!Title: Report
[FAILURE] oss-swift-package-osx [#452]
Build URL:https://ci.swift.org/job/oss-swift-package-osx/452/
Project:oss-swift-package-osx
Date of build:Mon, 09 Oct 2017 07:30:06 -0500
Build duration:1 hr 33 min
Identified problems:Regression test fa
For the Apple/swift git project, is there a map for each section, explaining
what it does and where all of its files are? The Xcode project gives dozens of
targets and manually inspecting them to figure out what each one does and how
they all fit together seems inefficient.
For instance, I wa
New issue found!Title: Report
[FAILURE] oss-swift-package-osx [#453]
Build URL:https://ci.swift.org/job/oss-swift-package-osx/453/
Project:oss-swift-package-osx
Date of build:Mon, 09 Oct 2017 09:56:06 -0500
Build duration:1 hr 35 min
Identified problems:Regression test fa
New issue found!Title: Report
[FAILURE] oss-swift-package-osx [#454]
Build URL:https://ci.swift.org/job/oss-swift-package-osx/454/
Project:oss-swift-package-osx
Date of build:Mon, 09 Oct 2017 11:47:17 -0500
Build duration:1 hr 3 min
Identified problems:Assertion failure:
I will note that the Makefile build is not something we test. What happens if
you drop -m from your build command, to use Ninja instead?
Jordan
> On Oct 8, 2017, at 22:36, Slava Pestov via swift-dev
> wrote:
>
> Hi Atul,
>
> The master branch is tested in CI, so any build failures are likel
UNREACHABLE executed at
/Users/buildnode/jenkins/workspace/oss-swift-package-osx/swift/lib/IRGen/IRGenDebugInfo.cpp:1408!
0 swift0x000106d477f8
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 40
1 swift0x000106d46746 llvm::sys::RunSignalHandlers
On Oct 8, 2017, at 3:30 PM, Erik Eckstein wrote:
>>> We definitely already have a heap->stack for classes in the guise of the
>>> StackPromotion optimization is that what you are talking about with the
>>> "array outlining" optimization? (outlining to me is referring to
>>> specifically code ou
> On Oct 7, 2017, at 2:01 PM, Chris Lattner wrote:
>
> Right. If we ignore source compatibility for the moment, it seems clear that
> the best callee side representation for varargs is a borrowing array slice
> (like llvm::ArrayRef or UnsafeBufferPointer). This provides the essential
> abs
Another dispatch failure:
Foundation/NSData.swift:19:8: error: module file was created by an older
version of the compiler; rebuild 'Dispatch' and try again:
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_04/buildbot_incremental/libdispatch-linux-x86_64/src/swift/Disp
Hi All-
Tomorrow, we will be temporarily bringing down the CI, starting around 1 PM,
California time, in order to upgrade Xcode and SDKs on the CI machines. We
expect the upgrade process to take an hour or two. We’ll send out a message
when the upgrade is complete.
Thanks!
nicole
_
On Oct 9, 2017, at 9:55 PM, Slava Pestov via swift-dev
wrote:
>> On Oct 7, 2017, at 2:01 PM, Chris Lattner wrote:
>> Right. If we ignore source compatibility for the moment, it seems clear
>> that the best callee side representation for varargs is a borrowing array
>> slice (like llvm::ArrayR
I tried the same build command I found in one of passing CI jobs for Ubuntu
16.04 (e.g.
https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_04/943/consoleFull
):
utils/build-script --assertions --release --test --validation-test
--lit-args=-v --build-subdir=buildbot_incremental --llb
13 matches
Mail list logo
