[swift-dev] Swift CI outage - Jan 10th 2016 5pm PST

[mishal_shah via swift-dev]

Swift CI (ci.swift.org) will be down on Jan 10th 2016 at 5pm PST for few hours. 

Thanks, 
Mishal Shah
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-lldb-dev] Swift CI outage - Jan 10th 2016 5pm PST

[mishal_shah via swift-lldb-dev]

Swift CI (ci.swift.org) will be down on Jan 10th 2016 at 5pm PST for few hours. 

Thanks, 
Mishal Shah
___
swift-lldb-dev mailing list
swift-lldb-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-lldb-dev

[swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - Ubuntu 14.04 (master) #86

[no-reply--- via swift-dev]

New issue found!Title: Report


  
  
 
 

 [FAILURE] oss-swift-package-linux-ubuntu-14_04 [#86] 


  Build URL:https://ci.swift.org/job/oss-swift-package-linux-ubuntu-14_04/86/
  Project:oss-swift-package-linux-ubuntu-14_04
  Date of build:Mon, 09 Jan 2017 18:04:50 -0800
  Build duration:4 min 41 sec







  





  Changes
  

  Commit 6ec5d23fcb2c7384009effa4e76cf0e3ace4a003 by hughbellars: Fix build warning compiling llbuild


  edit: lib/Commands/NinjaBuildCommand.cpp


  
 

  Commit 5ddbfc056e85f247cc806500b9497e78bcdab24c by daniel_dunbar: [llbuildui] Start on a simple database viewer.


  add: products/ui/README.md

  add: products/ui/setup.py

  add: products/ui/llbuildui/app.py

  add: products/ui/llbuildui/__init__.py


  
 

  Commit dd6745b7e30d39a2b22b64fa0017a92b24b03663 by daniel_dunbar: [ui] Add a database model for the current schema.


  add: products/ui/llbuildui/model.py


  
 

  Commit 6c256172837e1f02f0938d9a72fc81a16fc78115 by daniel_dunbar: [ui] Add database sessions to app.


  edit: products/ui/llbuildui/app.py

  add: products/ui/llbuildui/views.py

  add: products/ui/llbuildui/database.py

  edit: products/ui/README.md


  
 

  Commit 7b58ad1a443ab393d9ac63613ea58947704627af by daniel_dunbar: [ui] Add support for walking build graph.


  edit: products/ui/llbuildui/views.py

  edit: products/ui/llbuildui/model.py


  
 

  Commit aeaf0463af18b4573e83cb49ed2f6acc2ef8efb2 by hughbellars: Port stdlib/public/stubs/GlobalObjects to Windows


  edit: stdlib/public/stubs/GlobalObjects.cpp


  
 

  Commit 68bc423be39fc7339837d2c7c160508fddb2936b by florent.bruneau: Clang Importer: import all indirect fields.


  edit: lib/ClangImporter/ImportDecl.cpp

  edit: test/ClangImporter/ctypes_parse_union.swift

  edit: stdlib/public/SDK/GLKit/GLKMath.swift.gyb


  
 

  Commit 7f582c420db703abc89759bec433acee092b5e34 by nhawes: [indexer] When visiting a NominalTypeDecl, cover the type references in


  edit: tools/swift-ide-test/swift-ide-test.cpp

  edit: lib/Index/IndexSymbol.cpp

  edit: include/swift/AST/SourceEntityWalker.h

  edit: include/swift/Index/IndexSymbol.h

  edit: tools/swift-ide-test/CMakeLists.txt

  edit: include/swift/AST/ASTWalker.h

  edit: lib/IDE/SyntaxModel.cpp

  edit: lib/AST/SourceEntityWalker.cpp

  edit: lib/Index/Index.cpp

  edit: lib/AST/ASTWalker.cpp


  
 

  Commit 8c45e20d3f38c238917681dc9ddbbd4a53ba9707 by nhawes: [indexer] Add relations to IndexSymbol add a -print-indexed-symbols


  edit: tools/swift-ide-test/swift-ide-test.cpp

  add: test/Index/roles.swift

  edit: include/swift/Index/IndexSymbol.h

  add: test/Index/kinds.swift

  edit: include/swift/Index/IndexDataConsumer.h

  edit: tools/SourceKit/lib/SwiftLang/SwiftIndexing.cpp

  edit: lib/Index/Index.cpp


  
 

  Commit 4bc7435bb1cb877b0a0aaec78723a6719932413f by nhawes: [indexer] provide names for pseudo accessors too


  edit: test/Index/roles.swift

  edit: test/SourceKit/Indexing/index_bad_modulename.swift.response

  edit: test/SourceKit/Indexing/index_enum_case.swift.response

  edit: test/SourceKit/Indexing/index.swift.response

  edit: test/SourceKit/Indexing/index_forbid_typecheck.swift.response

  edit: test/SourceKit/Indexing/index_big_array.swift.response

  edit: lib/Index/Index.cpp


  
 

  Commit fdc74b457813d4a9e1ddbf883f4f759535bc085e by nhawes: [indexer] Add further tests for roles and relations


  edit: test/Index/roles.swift


  
 

  Commit d63269505b48f25a06997c5a8fb70bcac6f821a9 by practicalswift: [swiftc (56 vs. 5396)] Add crasher in swift::TupleType::get


  add: validation-test/compiler_crashers/28640-swift-tupletype-get-llvm-arrayref-swift-tupletypeelt-swift-astcontext-const.swift


  
 

  Commit 32ba5f24cb96834238180ad19da0ecc2fc722806 by nhawes: [indexer] Don't output implicit symbol names in order to maintain the


  edit: test/SourceKit/Indexing/index_bad_modulename.swift.response

  edit: test/SourceKit/Indexing/index_enum_case.swift.response

  edit: test/SourceKit/Indexing/index_big_array.swift.response

  edit: test/SourceKit/Indexing/index.swift.response

  edit: tools/SourceKit/lib/SwiftLang/SwiftIndexing.cpp

  edit: test/SourceKit/Indexing/index_forbid_typecheck.swift.response


  
 

  Commit 

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (master) #489

[Andrew Trick via swift-dev]

This crasher is still failing to crash on Ubuntu 14.04 (crashes as expected on 
16). I can’t imagine why the test would behave differently with the same target 
triple (x86_64-unknown-linux-gnu). Does anyone know how to REQUIRES: some-host? 
If not, I can lump this into deterministic-behavior.
-Andy

> On Jan 9, 2017, at 5:31 AM, no-re...@swift.org wrote:
> 
> New issue found!
> 
> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#489]
> 
> Build URL:
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/489/ 
> 
> Project:  oss-swift-incremental-RA-linux-ubuntu-14_04
> Date of build:Mon, 09 Jan 2017 04:59:29 -0800
> Build duration:   31 min
> Identified problems:
> 
> Compile Error: This build failed because of a compile error. Below is a list 
> of all errors in the build log:
> Indication 1 
> 
> Regression test failed: This build failed because a regression test in the 
> test suite FAILed. Below is a list of all errors:
> Indication 1 
> 
> Changes
> 
> Commit ed36d8f7e5d35b079f2bac3baf0e1818d44c8d32 by practicalswift:
> [swiftc (53 vs. 5396)] Add crasher in swift::TupleType::get
> 
> add: 
> validation-test/compiler_crashers/28637-swift-tupletype-get-llvm-arrayref-swift-tupletypeelt-swift-astcontext-const.swift

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] index indexes and ranges of String

[Carlos García via swift-dev]

Hi,

I think this is important enough and useful for we to be in the core standard 
library

extension String {

func index(of string: String, options: String.CompareOptions = .literal) -> 
String.Index? {
return range(of: string, options: options)?.lowerBound
}

func indexes(of string: String, options: String.CompareOptions = .literal) 
-> [String.Index] {
var result: [String.Index] = []
var start = startIndex
while let range = range(of: string, options: options, range: 
start.. [Range] {
var result: [Range] = []
var start = startIndex
while let range = range(of: string, options: options, range: 
start..

Carlos García___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-corelibs-dev] Question about NSDecimalCopy

[Morten Bek Ditlevsen via swift-corelibs-dev]

Hi list,
I was looking at the NSDecimal.swift to learn a bit about the implementation of 
the Decimal type.
I get that a lot of the API in this type exists for compatibility reasons with 
the C implementation.

But I was wondering about how the NSDecimalCopy function differs from a simple 
assignment of one Decimal value to another.

NSDecimalCopy simply assigns each field of the struct one by one, so when would 
it ever be preferable to performing a simple assignment?

So basically my question is - is there any difference in the result of 
performing:

var a: Decimal = 1
var b: Decimal = 2
NSDecimalCopy(, )

and 
var a: Decimal = 1
var b: Decimal = 2
b = a

Secondly - if there is no difference in the result - is it not more performant 
to assign the value directly?

This question also raised a question about Swift internals: If you have a pure 
value type (no nested reference types): Does an assignment then simply copy a 
chunk of memory with the size of the struct? Or is each field assigned/copied 
recursively?

Sincerely,
/morten
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #7835

[Andrew Trick via swift-dev]

> On Jan 8, 2017, at 11:15 PM, Slava Pestov  wrote:
> 
> Assertion failed: (hasVal), function getValue, file 
> /Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/llvm/include/llvm/ADT/Optional.h,
>  line 122.
> 
> This has been failing on and off all day… has anyone tried reproducing it 
> locally?
> 
> Slava

No, I don’t know what started this either.
Filed  Public CI build bot failures: Assert 
ADT/Optional.h, line 122: LSValue::reduceInner.
-Andy

> 
>> On Jan 8, 2017, at 11:11 PM, no-re...@swift.org  
>> wrote:
>> 
>> [FAILURE] oss-swift-incremental-RA-osx [#7835]
>> 
>> Build URL:   https://ci.swift.org/job/oss-swift-incremental-RA-osx/7835/ 
>> 
>> Project: oss-swift-incremental-RA-osx
>> Date of build:   Sun, 08 Jan 2017 23:05:01 -0800
>> Build duration:  6 min 4 sec
>> Identified problems:
>> 
>> Assertion failure: This build failed because of an assertion failure. Below 
>> is a list of all errors in the build log:
>> Indication 1 
>> 
>> Changes
>> 
>> Commit 844765b2fc7217d49712e85b8dec5e92e1492db7 by spestov:
>> SILOptimizer: Clean up hasDynamicSelfTypes() and
>> 
>> edit: include/swift/SILOptimizer/Utils/Local.h
>> edit: lib/SILOptimizer/Transforms/PerformanceInliner.cpp
>> edit: lib/SILOptimizer/IPO/UsePrespecialized.cpp
>> edit: lib/SILOptimizer/Utils/Generics.cpp
>> edit: lib/SILOptimizer/Utils/Local.cpp
>> 
>> Commit 7731d4c6cb406f808a3ea1c2519e2481e858e7fd by spestov:
>> Sema: Remove some unnecessary calls to getCanonicalType()
>> 
>> edit: lib/IDE/CodeCompletion.cpp
>> edit: lib/Sema/ConstraintSystem.cpp
>> edit: lib/AST/GenericSignature.cpp
>> edit: lib/AST/Availability.cpp
>> edit: lib/AST/ProtocolConformance.cpp
>> edit: lib/Sema/TypeCheckAttr.cpp
>> edit: lib/Sema/PlaygroundTransform.cpp
>> edit: lib/Sema/TypeCheckStmt.cpp
>> edit: lib/Sema/CSApply.cpp
>> edit: lib/Sema/CSDiag.cpp
>> edit: lib/Sema/TypeCheckProtocol.cpp
>> edit: lib/IDE/TypeReconstruction.cpp
>> edit: lib/AST/Substitution.cpp
>> edit: lib/AST/DiagnosticEngine.cpp
>> edit: lib/AST/ASTVerifier.cpp
>> edit: lib/Sema/CSGen.cpp
>> 
>> Commit 208dec74d01621880895d7b05fb1b38a69c68d2f by spestov:
>> Sema: Validate addressors when an AbstractStorageDecl is validated
>> 
>> edit: lib/Sema/CodeSynthesis.cpp
>> edit: lib/Sema/TypeCheckDecl.cpp
>> 
>> Commit 02185c30ee361118f457663d4fb0211bd24abfbb by spestov:
>> Sema: When validating members for layout, skip certain members
>> 
>> edit: lib/Sema/TypeChecker.cpp
>> add: validation-test/compiler_scale/enum_members.gyb
>> add: validation-test/compiler_scale/struct_members.gyb
>> 
>> Commit 6c75bf8dc5072d65f204b5724930523376366c20 by spestov:
>> Update source-stability test
>> 
>> edit: test/api-digester/source-stability.swift.expected
> 

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev