Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread mishal_shah via swift-dev
Lib dispatch test failed, however next build passed 
(https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/ 
)


Testsuite summary for libkqueue 2.0.4

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

Thanks,
Mishal Shah
> On Aug 30, 2016, at 11:31 AM, Jordan Rose  wrote:
> 
> I'm seeing this on all the Linux smoke tests right now. :-( Any ideas, 
> Mishal? Should we just try wiping the workspace?
> 
> Jordan
> 
> 
>> On Aug 29, 2016, at 23:34, Jacob Bandes-Storch > > wrote:
>> 
>> Not really sure what's going on here. The only failure I see is this, but I 
>> don't know what actually failed:
>> 
>> make[3]: *** [test-suite.log] Error 1
>> make[3]: Leaving directory 
>> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>> make[2]: *** [check-TESTS] Error 2
>> make[2]: Leaving directory 
>> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>> make[1]: *** [check-am] Error 2
>> make[1]: Leaving directory 
>> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>> make: *** [check-recursive] Error 1
>> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>>  fatal error: command terminated with a non-zero exit status 2, aborting
>> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>>  fatal error: command terminated with a non-zero exit status 1, aborting
>> 
>> 
>> On Mon, Aug 29, 2016 at 11:18 PM, > > wrote:
>> [FAILURE] oss-swift-3.0-incremental-RA-linux-ubuntu-14_04 [#177]
>> 
>> Build URL:   
>> https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/
>>  
>> 
>> Project: oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
>> Date of build:   Mon, 29 Aug 2016 23:06:18 -0700
>> Build duration:  11 min
>> Tests:
>> 
>> Name: Swift(linux-x86_64)
>> Failed: 0 test(s), Passed: 8233 test(s), Total: 8233 test(s)
>> Name: Swift-Unit
>> Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
>> 
>> Changes
>> 
>> Commit 41eb798f035aff1e705ec6d33a1f0ab2174fd978 by jordan_rose:
>> [ClangImporter] Predefine __swift__ in imported (Obj)C code. (#4510)
>> 
>> edit: test/ClangModules/Inputs/custom-modules/module.map
>> edit: include/swift/Basic/Version.h
>> add: test/ClangModules/Inputs/custom-modules/PredefinedMacros.h
>> edit: lib/ClangImporter/ClangImporter.cpp
>> add: test/ClangModules/predefined_macros.swift
>> edit: lib/Basic/Version.cpp
>> 
>> Commit 11999525bf57a87b818366438d6c8b68e886e3ae by jacob:
>> [QoI] diagnose initializers written as typed patterns (SR-1461)
>> 
>> add: test/Parse/diagnose_initializer_as_typed_pattern.swift
>> edit: lib/Parse/ParsePattern.cpp
>> edit: include/swift/AST/DiagnosticsParse.def
>> 
>> Commit 2c998bda9c65343df0e1679b33f64f33af9725db by jacob:
>> [QoI] fix diagnosis of non-Optional enum used in optional pattern
>> 
>> edit: lib/Sema/TypeCheckPattern.cpp
>> edit: test/SILGen/statements.swift
>> edit: test/stmt/if_while_var.swift
>> 
>> Commit fd8f6f537d223ad3ae5b588a1da47780a307d2c6 by xiaodi.wu:
>> [Swift 3.0.1] Fix decimal
>> 
>> edit: stdlib/public/SDK/Foundation/Decimal.swift
>> edit: test/Interpreter/SDK/NSDecimal.swift
>> 
>> Commit 29153b5bdf48d1bdd33c346bab87f49b1fa144ca by xiaodi.wu:
>> Fix-up (line ending)
>> 
>> edit: test/Interpreter/SDK/NSDecimal.swift
>> 
>> 
> 

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


[swift-dev] Updating llvm/clang stable branches

2016-08-31 Thread Michael Gottesman via swift-dev
Hello swift-dev!

We are going to be performing an update to the llvm/clang stable branches 
within the next couple of days. I will send out an email before I pull the 
trigger. We will be using a -s ours merge so if you run update-checkout (or 
even just git pull), everything should fast forward appropriately.

If you have any questions, please feel free to send me an email (or respond to 
this one).

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


Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread Chris Bailey via swift-dev
Each of the libdispatch tests generates a log file that can be grabbed to 
see more detail on a failure. You can find the .log files in:
buildbot_linux/libdispatch-linux-x86_64/tests/


Regards



C (Chris) Bailey
 

Senior Technical Staff Member (STSM)
 Hursley Park
Runtime Technologies for Java, Node.js and Swift
 Winchester, Hampshire SO21 2JN
IBM Software Group
 United Kingdom

Phone:
+44-1962-817078
IBM SDKs for Java™

Mobile:
+44-7738-310815 (272022)
IBM SDKs for Node.js™

e-mail:
bail...@uk.ibm.com
IBM Monitoring and Diagnostic Tools

Find me on:   
 





From:   mishal_shah 
To: Tony Parker 
Cc: Chris Bailey/UK/IBM@IBMGB, Pushkar N Kulkarni 
, Jordan Rose , swift-dev 
, Xiaodi Wu , Jacob 
Bandes-Storch 
Date:   30/08/2016 22:08
Subject:Re: [Swift CI] Build Failure: 0. OSS - Swift Incremental 
RA - Ubuntu 14.04 (swift 3.0) #177
Sent by:mishal_s...@apple.com



I am rerunning it on different system to see if this is only happening on 
one system. 

Console: 
https://ci.swift.org/view/Pull%20Request/job/swift-PR-Linux-smoke-test/929/consoleFull

make bsdtestharness bsdtestsummarize dispatch_apply dispatch_api 
dispatch_c99 dispatch_debug dispatch_queue_finalizer dispatch_group 
dispatch_overcommit dispatch_plusplus dispatch_context_for_key 
dispatch_after dispatch_timer dispatch_timer_short dispatch_timer_timeout 
dispatch_sema dispatch_suspend_timer dispatch_timer_bit31 
dispatch_timer_bit63 dispatch_timer_set_time dispatch_starfish 
dispatch_data dispatch_io_net dispatch_select make[2]: Entering directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
 
make[2]: `bsdtestharness' is up to date. make[2]: `bsdtestsummarize' is up 
to date. make[2]: `dispatch_apply' is up to date. make[2]: `dispatch_api' 
is up to date. make[2]: `dispatch_c99' is up to date. make[2]: 
`dispatch_debug' is up to date. make[2]: `dispatch_queue_finalizer' is up 
to date. make[2]: `dispatch_group' is up to date. make[2]: 
`dispatch_overcommit' is up to date. make[2]: `dispatch_plusplus' is up to 
date. make[2]: `dispatch_context_for_key' is up to date. make[2]: 
`dispatch_after' is up to date. make[2]: `dispatch_timer' is up to date. 
make[2]: `dispatch_timer_short' is up to date. make[2]: 
`dispatch_timer_timeout' is up to date. make[2]: `dispatch_sema' is up to 
date. make[2]: `dispatch_suspend_timer' is up to date. make[2]: 
`dispatch_timer_bit31' is up to date. make[2]: `dispatch_timer_bit63' is 
up to date. make[2]: `dispatch_timer_set_time' is up to date. make[2]: 
`dispatch_starfish' is up to date. make[2]: `dispatch_data' is up to date. 
make[2]: `dispatch_io_net' is up to date. make[2]: `dispatch_select' is up 
to date. make[2]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
 
make check-TESTS make[2]: Entering directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
 
make[3]: Entering directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
 
FAIL: dispatch_apply FAIL: dispatch_api FAIL: dispatch_c99 FAIL: 
dispatch_debug FAIL: dispatch_queue_finalizer FAIL: dispatch_group FAIL: 
dispatch_overcommit FAIL: dispatch_plusplus FAIL: dispatch_context_for_key 
FAIL: dispatch_after FAIL: dispatch_timer FAIL: dispatch_timer_short FAIL: 
dispatch_timer_timeout FAIL: dispatch_sema FAIL: dispatch_suspend_timer 
FAIL: dispatch_timer_bit31 FAIL: dispatch_timer_bit63 FAIL: 
dispatch_timer_set_time FAIL: dispatch_starfish FAIL: dispatch_data FAIL: 
dispatch_io_net FAIL: dispatch_select make[4]: Entering directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
 
make[4]: Nothing to be done for `all'. make[4]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
 
 
Testsuite summary for libdispatch 1.3 
 
# TOTAL: 22 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 22 # XPASS: 0 # ERROR: 
0 
 
See tests/test-suite.log Please report to https://bugs.swift.org 
 
make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
 
make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
 
make[1]: *** [chec

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread Jordan Rose via swift-dev
I'm seeing this on all the Linux smoke tests right now. :-( Any ideas, Mishal? 
Should we just try wiping the workspace?

Jordan


> On Aug 29, 2016, at 23:34, Jacob Bandes-Storch  
> wrote:
> 
> Not really sure what's going on here. The only failure I see is this, but I 
> don't know what actually failed:
> 
> make[3]: *** [test-suite.log] Error 1
> make[3]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
> make[2]: *** [check-TESTS] Error 2
> make[2]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
> make[1]: *** [check-am] Error 2
> make[1]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
> make: *** [check-recursive] Error 1
> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>  fatal error: command terminated with a non-zero exit status 2, aborting
> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>  fatal error: command terminated with a non-zero exit status 1, aborting
> 
> 
> On Mon, Aug 29, 2016 at 11:18 PM,  > wrote:
> [FAILURE] oss-swift-3.0-incremental-RA-linux-ubuntu-14_04 [#177]
> 
> Build URL:
> https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/ 
> 
> Project:  oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
> Date of build:Mon, 29 Aug 2016 23:06:18 -0700
> Build duration:   11 min
> Tests:
> 
> Name: Swift(linux-x86_64)
> Failed: 0 test(s), Passed: 8233 test(s), Total: 8233 test(s)
> Name: Swift-Unit
> Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
> 
> Changes
> 
> Commit 41eb798f035aff1e705ec6d33a1f0ab2174fd978 by jordan_rose:
> [ClangImporter] Predefine __swift__ in imported (Obj)C code. (#4510)
> 
> edit: test/ClangModules/Inputs/custom-modules/module.map
> edit: include/swift/Basic/Version.h
> add: test/ClangModules/Inputs/custom-modules/PredefinedMacros.h
> edit: lib/ClangImporter/ClangImporter.cpp
> add: test/ClangModules/predefined_macros.swift
> edit: lib/Basic/Version.cpp
> 
> Commit 11999525bf57a87b818366438d6c8b68e886e3ae by jacob:
> [QoI] diagnose initializers written as typed patterns (SR-1461)
> 
> add: test/Parse/diagnose_initializer_as_typed_pattern.swift
> edit: lib/Parse/ParsePattern.cpp
> edit: include/swift/AST/DiagnosticsParse.def
> 
> Commit 2c998bda9c65343df0e1679b33f64f33af9725db by jacob:
> [QoI] fix diagnosis of non-Optional enum used in optional pattern
> 
> edit: lib/Sema/TypeCheckPattern.cpp
> edit: test/SILGen/statements.swift
> edit: test/stmt/if_while_var.swift
> 
> Commit fd8f6f537d223ad3ae5b588a1da47780a307d2c6 by xiaodi.wu:
> [Swift 3.0.1] Fix decimal
> 
> edit: stdlib/public/SDK/Foundation/Decimal.swift
> edit: test/Interpreter/SDK/NSDecimal.swift
> 
> Commit 29153b5bdf48d1bdd33c346bab87f49b1fa144ca by xiaodi.wu:
> Fix-up (line ending)
> 
> edit: test/Interpreter/SDK/NSDecimal.swift
> 
> 

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


Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread mishal_shah via swift-dev
After clean build its still failing.

Tony, do you know who can help us look into these failures?


Testsuite summary for libdispatch 1.3

# TOTAL: 22
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  22
# XPASS: 0
# ERROR: 0

> On Aug 30, 2016, at 11:58 AM, Jordan Rose  wrote:
> 
> …but the smoke tests are still failing.
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/925/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/926/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/927/ 
> 
> 
> (923 passed, for some reason.)
> 
> 
>> On Aug 30, 2016, at 11:55, mishal_shah > > wrote:
>> 
>> Lib dispatch test failed, however next build passed 
>> (https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/
>>  
>> )
>> 
>> 
>> Testsuite summary for libkqueue 2.0.4
>> 
>> # TOTAL: 1
>> # PASS:  0
>> # SKIP:  0
>> # XFAIL: 0
>> # FAIL:  1
>> # XPASS: 0
>> # ERROR: 0
>> 
>> Thanks,
>> Mishal Shah
>>> On Aug 30, 2016, at 11:31 AM, Jordan Rose >> > wrote:
>>> 
>>> I'm seeing this on all the Linux smoke tests right now. :-( Any ideas, 
>>> Mishal? Should we just try wiping the workspace?
>>> 
>>> Jordan
>>> 
>>> 
 On Aug 29, 2016, at 23:34, Jacob Bandes-Storch >>> > wrote:
 
 Not really sure what's going on here. The only failure I see is this, but 
 I don't know what actually failed:
 
 make[3]: *** [test-suite.log] Error 1
 make[3]: Leaving directory 
 `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make[2]: *** [check-TESTS] Error 2
 make[2]: Leaving directory 
 `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make[1]: *** [check-am] Error 2
 make[1]: Leaving directory 
 `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make: *** [check-recursive] Error 1
 /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
  fatal error: command terminated with a non-zero exit status 2, aborting
 /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
  fatal error: command terminated with a non-zero exit status 1, aborting
 
 
 On Mon, Aug 29, 2016 at 11:18 PM, >>> > wrote:
 [FAILURE] oss-swift-3.0-incremental-RA-linux-ubuntu-14_04 [#177]
 
 Build URL: 
 https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/
  
 
 Project:   oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
 Date of build: Mon, 29 Aug 2016 23:06:18 -0700
 Build duration:11 min
 Tests:
 
 Name: Swift(linux-x86_64)
 Failed: 0 test(s), Passed: 8233 test(s), Total: 8233 test(s)
 Name: Swift-Unit
 Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
 
 Changes
 
 Commit 41eb798f035aff1e705ec6d33a1f0ab2174fd978 by jordan_rose:
 [ClangImporter] Predefine __swift__ in imported (Obj)C code. (#4510)
 
 edit: test/ClangModules/Inputs/custom-modules/module.map
 edit: include/swift/Basic/Version.h
 add: test/ClangModules/Inputs/custom-modules/PredefinedMacros.h
 edit: lib/ClangImporter/ClangImporter.cpp
 add: test/ClangModules/predefined_macros.swift
 edit: lib/Basic/Version.cpp
 
 Commit 11999525bf57a87b818366438d6c8b68e886e3ae by jacob:
 [QoI] diagnose initializers written as typed patterns (SR-1461)
 
 add: test/Parse/diagnose_initializer_as_typed_pattern.swift
 edit: lib/Parse/ParsePattern.cpp
 edit: include/swift/AST/DiagnosticsParse.def
 
 Commit 2c998bda9c65343df0e1679b33f64f33af9725db by jacob:
 [QoI] fix diagnosis of non-Optional enum used in optional pattern
 
 edit: lib/Sema/TypeCheckPattern.cpp
 edit: test/SILGen/statements.swift
 edit: test/stmt/if_while_var.swift
 
 Commit fd8f6f537d223ad3ae5b588a1da47780a307d2

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread Tony Parker via swift-dev
Is there any more detailed output here? All I see above your summary is every 
test failing with no additional output...

Is this on a different machine or different configuration from master?

- Tony

> On Aug 30, 2016, at 1:51 PM, mishal_shah  wrote:
> 
> After clean build its still failing.
> 
> Tony, do you know who can help us look into these failures?
> 
> 
> Testsuite summary for libdispatch 1.3
> 
> # TOTAL: 22
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  22
> # XPASS: 0
> # ERROR: 0
> 
>> On Aug 30, 2016, at 11:58 AM, Jordan Rose > > wrote:
>> 
>> …but the smoke tests are still failing.
>> 
>> https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/ 
>> 
>> https://ci.swift.org/job/swift-PR-Linux-smoke-test/925/ 
>> 
>> https://ci.swift.org/job/swift-PR-Linux-smoke-test/926/ 
>> 
>> https://ci.swift.org/job/swift-PR-Linux-smoke-test/927/ 
>> 
>> 
>> (923 passed, for some reason.)
>> 
>> 
>>> On Aug 30, 2016, at 11:55, mishal_shah >> > wrote:
>>> 
>>> Lib dispatch test failed, however next build passed 
>>> (https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/
>>>  
>>> )
>>> 
>>> 
>>> Testsuite summary for libkqueue 2.0.4
>>> 
>>> # TOTAL: 1
>>> # PASS:  0
>>> # SKIP:  0
>>> # XFAIL: 0
>>> # FAIL:  1
>>> # XPASS: 0
>>> # ERROR: 0
>>> 
>>> Thanks,
>>> Mishal Shah
 On Aug 30, 2016, at 11:31 AM, Jordan Rose >>> > wrote:
 
 I'm seeing this on all the Linux smoke tests right now. :-( Any ideas, 
 Mishal? Should we just try wiping the workspace?
 
 Jordan
 
 
> On Aug 29, 2016, at 23:34, Jacob Bandes-Storch  > wrote:
> 
> Not really sure what's going on here. The only failure I see is this, but 
> I don't know what actually failed:
> 
> make[3]: *** [test-suite.log] Error 1
> make[3]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
> make[2]: *** [check-TESTS] Error 2
> make[2]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
> make[1]: *** [check-am] Error 2
> make[1]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
> make: *** [check-recursive] Error 1
> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>  fatal error: command terminated with a non-zero exit status 2, aborting
> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>  fatal error: command terminated with a non-zero exit status 1, aborting
> 
> 
> On Mon, Aug 29, 2016 at 11:18 PM,  > wrote:
> [FAILURE] oss-swift-3.0-incremental-RA-linux-ubuntu-14_04 [#177]
> 
> Build URL:
> https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/
>  
> 
> Project:  oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
> Date of build:Mon, 29 Aug 2016 23:06:18 -0700
> Build duration:   11 min
> Tests:
> 
> Name: Swift(linux-x86_64)
> Failed: 0 test(s), Passed: 8233 test(s), Total: 8233 test(s)
> Name: Swift-Unit
> Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
> 
> Changes
> 
> Commit 41eb798f035aff1e705ec6d33a1f0ab2174fd978 by jordan_rose:
> [ClangImporter] Predefine __swift__ in imported (Obj)C code. (#4510)
> 
> edit: test/ClangModules/Inputs/custom-modules/module.map
> edit: include/swift/Basic/Version.h
> add: test/ClangModules/Inputs/custom-modules/PredefinedMacros.h
> edit: lib/ClangImporter/ClangImporter.cpp
> add: test/ClangModules/predefined_macros.swift
> edit: lib/Basic/Version.cpp
> 
> Commit 11999525bf57a87b818366438d6c8b68e886e3ae by jacob:
> [QoI] diagnose initializers written as typed patterns (SR-1461)
> 
> add: test/Parse/diagnose_initializer_as_typed_

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread mishal_shah via swift-dev
I am rerunning it on different system to see if this is only happening on one 
system. 

Console: 
https://ci.swift.org/view/Pull%20Request/job/swift-PR-Linux-smoke-test/929/consoleFull
 


make  bsdtestharness bsdtestsummarize dispatch_apply dispatch_api dispatch_c99 
dispatch_debug dispatch_queue_finalizer dispatch_group dispatch_overcommit 
dispatch_plusplus dispatch_context_for_key dispatch_after dispatch_timer 
dispatch_timer_short dispatch_timer_timeout dispatch_sema 
dispatch_suspend_timer dispatch_timer_bit31 dispatch_timer_bit63 
dispatch_timer_set_time dispatch_starfish dispatch_data dispatch_io_net 
dispatch_select  
make[2]: Entering directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
make[2]: `bsdtestharness' is up to date.
make[2]: `bsdtestsummarize' is up to date.
make[2]: `dispatch_apply' is up to date.
make[2]: `dispatch_api' is up to date.
make[2]: `dispatch_c99' is up to date.
make[2]: `dispatch_debug' is up to date.
make[2]: `dispatch_queue_finalizer' is up to date.
make[2]: `dispatch_group' is up to date.
make[2]: `dispatch_overcommit' is up to date.
make[2]: `dispatch_plusplus' is up to date.
make[2]: `dispatch_context_for_key' is up to date.
make[2]: `dispatch_after' is up to date.
make[2]: `dispatch_timer' is up to date.
make[2]: `dispatch_timer_short' is up to date.
make[2]: `dispatch_timer_timeout' is up to date.
make[2]: `dispatch_sema' is up to date.
make[2]: `dispatch_suspend_timer' is up to date.
make[2]: `dispatch_timer_bit31' is up to date.
make[2]: `dispatch_timer_bit63' is up to date.
make[2]: `dispatch_timer_set_time' is up to date.
make[2]: `dispatch_starfish' is up to date.
make[2]: `dispatch_data' is up to date.
make[2]: `dispatch_io_net' is up to date.
make[2]: `dispatch_select' is up to date.
make[2]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
make  check-TESTS
make[2]: Entering directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
make[3]: Entering directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
FAIL: dispatch_apply
FAIL: dispatch_api
FAIL: dispatch_c99
FAIL: dispatch_debug
FAIL: dispatch_queue_finalizer
FAIL: dispatch_group
FAIL: dispatch_overcommit
FAIL: dispatch_plusplus
FAIL: dispatch_context_for_key
FAIL: dispatch_after
FAIL: dispatch_timer
FAIL: dispatch_timer_short
FAIL: dispatch_timer_timeout
FAIL: dispatch_sema
FAIL: dispatch_suspend_timer
FAIL: dispatch_timer_bit31
FAIL: dispatch_timer_bit63
FAIL: dispatch_timer_set_time
FAIL: dispatch_starfish
FAIL: dispatch_data
FAIL: dispatch_io_net
FAIL: dispatch_select
make[4]: Entering directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'

Testsuite summary for libdispatch 1.3

# TOTAL: 22
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  22
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to https://bugs.swift.org 

make[3]: *** [test-suite.log] Error 1
make[3]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
make[2]: *** [check-TESTS] Error 2
make[2]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory 
`/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
make: *** [check-recursive] Error 1
/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/swift/utils/build-script:
 fatal error: command terminated with a non-zero exit status 2, aborting
/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/swift/utils/build-script:
 fatal error: command terminated with a non-zero exit status 1, aborting
Build step 'Execute shell' marked build as failure
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 
'branch-master/buildbot_linux/swift-linux-x86_64/swift-test-results/x86_64-unknown-linux-gnu/**

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread mishal_shah via swift-dev
Next few build passed, next time I will look into the logs. 

Thanks, 
Mishal Shah
> On Aug 30, 2016, at 3:03 PM, Chris Bailey  wrote:
> 
> Each of the libdispatch tests generates a log file that can be grabbed to see 
> more detail on a failure. You can find the .log files in: 
> buildbot_linux/libdispatch-linux-x86_64/tests/ 
> 
> 
> Regards 
> C (Chris) Bailey  
> 
> Senior Technical Staff Member (STSM)   Hursley Park
> Runtime Technologies for Java, Node.js and Swift   Winchester, Hampshire 
> SO21 2JN
> IBM Software Group United Kingdom 
> Phone:+44-1962-817078 IBM SDKs for Java™ 
>   
> Mobile:   +44-7738-310815 (272022)IBM SDKs for Node.js™ 
>   
> e-mail:   bail...@uk.ibm.com  IBM Monitoring and Diagnostic Tools 
> 
> Find me on:  
>   
> 
>  
> 
> 
> 
> 
> 
> 
> From:mishal_shah  
> To:Tony Parker  
> Cc:Chris Bailey/UK/IBM@IBMGB, Pushkar N Kulkarni 
> , Jordan Rose , swift-dev 
> , Xiaodi Wu , Jacob Bandes-Storch 
>  
> Date:30/08/2016 22:08 
> Subject:Re: [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - 
> Ubuntu 14.04 (swift 3.0) #177 
> Sent by:mishal_s...@apple.com 
> 
> 
> 
> I am rerunning it on different system to see if this is only happening on one 
> system. 
> 
> Console: 
> https://ci.swift.org/view/Pull%20Request/job/swift-PR-Linux-smoke-test/929/consoleFull
>  
> 
>  
> 
> make bsdtestharness bsdtestsummarize dispatch_apply dispatch_api dispatch_c99 
> dispatch_debug dispatch_queue_finalizer dispatch_group dispatch_overcommit 
> dispatch_plusplus dispatch_context_for_key dispatch_after dispatch_timer 
> dispatch_timer_short dispatch_timer_timeout dispatch_sema 
> dispatch_suspend_timer dispatch_timer_bit31 dispatch_timer_bit63 
> dispatch_timer_set_time dispatch_starfish dispatch_data dispatch_io_net 
> dispatch_select make[2]: Entering directory 
> `/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
>  make[2]: `bsdtestharness' is up to date. make[2]: `bsdtestsummarize' is up 
> to date. make[2]: `dispatch_apply' is up to date. make[2]: `dispatch_api' is 
> up to date. make[2]: `dispatch_c99' is up to date. make[2]: `dispatch_debug' 
> is up to date. make[2]: `dispatch_queue_finalizer' is up to date. make[2]: 
> `dispatch_group' is up to date. make[2]: `dispatch_overcommit' is up to date. 
> make[2]: `dispatch_plusplus' is up to date. make[2]: 
> `dispatch_context_for_key' is up to date. make[2]: `dispatch_after' is up to 
> date. make[2]: `dispatch_timer' is up to date. make[2]: 
> `dispatch_timer_short' is up to date. make[2]: `dispatch_timer_timeout' is up 
> to date. make[2]: `dispatch_sema' is up to date. make[2]: 
> `dispatch_suspend_timer' is up to date. make[2]: `dispatch_timer_bit31' is up 
> to date. make[2]: `dispatch_timer_bit63' is up to date. make[2]: 
> `dispatch_timer_set_time' is up to date. make[2]: `dispatch_starfish' is up 
> to date. make[2]: `dispatch_data' is up to date. make[2]: `dispatch_io_net' 
> is up to date. make[2]: `dispatch_select' is up to date. make[2]: Leaving 
> directory 
> `/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
>  make check-TESTS make[2]: Entering directory 
> `/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
>  make[3]: Entering directory 
> `/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
>  FAIL: dispatch_apply FAIL: dispatch_api FAIL: dispatch_c99 FAIL: 
> dispatch_debug FAIL: dispatch_queue_finalizer FAIL: dispatch_group FAIL: 
> dispatch_overcommit FAIL: dispatch_plusplus FAIL: dispatch_context_for_key 
> FAIL: dispatch_after FAIL: dispatch_timer FAIL: dispatch_timer_short FAIL: 
> dispatch_timer_timeout FAIL: dispatch_sema FAIL: dispatch_suspend_timer FAIL: 
> dispatch_timer_bit31 FAIL: dispatch_timer_bit63 FAIL: dispatch_timer_set_time 
> FAIL: dispatch_starfish FAIL: dispatch_data FAIL: dispatch_io_net FAIL: 
> dispatch_select make[4]: Entering directory 
> `/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
>  make[4]: Nothing to be done for `all'. make[4]: Leaving directory 
> `/home/buildnode/disk2/workspace/swift-PR-Linux-smoke-test/branch-master/buildbot_linux/libdispatch-linux-x86_64/tests'
>   
> Testsuite summary for libdispatch 1.3 
> 

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread David P Grove via swift-dev
Detailed output from a failed test would be useful.  One of the .log files

I'd expect that if every test is failing we probably have a linkage problem
or something similar.

--dave




From:   Tony Parker via swift-dev 
To: mishal_shah , Chris Bailey
, Pushkar N Kulkarni

Cc: Jacob Bandes-Storch , swift-dev
, Xiaodi Wu 
Date:   08/31/2016 01:01 PM
Subject:Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift
Incremental RA - Ubuntu 14.04 (swift 3.0) #177
Sent by:swift-dev-boun...@swift.org



Is there any more detailed output here? All I see above your summary is
every test failing with no additional output...

Is this on a different machine or different configuration from master?

- Tony

  On Aug 30, 2016, at 1:51 PM, mishal_shah 
  wrote:

  After clean build its still failing.

  Tony, do you know who can help us look into these failures?

  

 Testsuite summary for libdispatch 1.3
  

 # TOTAL: 22 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 22 # XPASS: 0 # ERROR:
  0

On Aug 30, 2016, at 11:58 AM, Jordan Rose <
jordan_r...@apple.com> wrote:

…but the smoke tests are still failing.

https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/925/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/926/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/927/

(923 passed, for some reason.)


  On Aug 30, 2016, at 11:55, mishal_shah <
  mishal_s...@apple.com> wrote:

  Lib dispatch test failed, however next build passed (
  
https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/
  )

  

  Testsuite summary for libkqueue 2.0.4
  

  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  Thanks,
  Mishal Shah
On Aug 30, 2016, at 11:31 AM, Jordan Rose <
jordan_r...@apple.com> wrote:

I'm seeing this on all the Linux smoke tests right
now. :-( Any ideas, Mishal? Should we just try
wiping the workspace?

Jordan


  On Aug 29, 2016, at 23:34, Jacob
  Bandes-Storch 
  wrote:

  Not really sure what's going on here. The
  only failure I see is this, but I don't know
  what actually failed:

  make[3]: *** [test-suite.log] Error 1 make
  [3]: Leaving directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make[1]: *** [check-am] Error 2 make[1]: Leaving directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make: *** [check-recursive] Error
  1 
/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
 fatal error: command terminated with a non-zero exit status 2,
  aborting 
/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
 fatal error: command terminated with a non-zero exit status 1, aborting


  On Mon, Aug 29, 2016 at 11:18 PM, <
  no-re...@swift.org> wrote:
[FAILURE]
oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
 [#177]

 
  Build URL:   
https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/ 

 
   Project:oss-swift-3

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread Jordan Rose via swift-dev
…but the smoke tests are still failing.

https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/925/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/926/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/927/

(923 passed, for some reason.)


> On Aug 30, 2016, at 11:55, mishal_shah  wrote:
> 
> Lib dispatch test failed, however next build passed 
> (https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/
>  
> )
> 
> 
> Testsuite summary for libkqueue 2.0.4
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> Thanks,
> Mishal Shah
>> On Aug 30, 2016, at 11:31 AM, Jordan Rose > > wrote:
>> 
>> I'm seeing this on all the Linux smoke tests right now. :-( Any ideas, 
>> Mishal? Should we just try wiping the workspace?
>> 
>> Jordan
>> 
>> 
>>> On Aug 29, 2016, at 23:34, Jacob Bandes-Storch >> > wrote:
>>> 
>>> Not really sure what's going on here. The only failure I see is this, but I 
>>> don't know what actually failed:
>>> 
>>> make[3]: *** [test-suite.log] Error 1
>>> make[3]: Leaving directory 
>>> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>>> make[2]: *** [check-TESTS] Error 2
>>> make[2]: Leaving directory 
>>> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>>> make[1]: *** [check-am] Error 2
>>> make[1]: Leaving directory 
>>> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>>> make: *** [check-recursive] Error 1
>>> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>>>  fatal error: command terminated with a non-zero exit status 2, aborting
>>> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>>>  fatal error: command terminated with a non-zero exit status 1, aborting
>>> 
>>> 
>>> On Mon, Aug 29, 2016 at 11:18 PM, >> > wrote:
>>> [FAILURE] oss-swift-3.0-incremental-RA-linux-ubuntu-14_04 [#177]
>>> 
>>> Build URL:  
>>> https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/
>>>  
>>> 
>>> Project:oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
>>> Date of build:  Mon, 29 Aug 2016 23:06:18 -0700
>>> Build duration: 11 min
>>> Tests:
>>> 
>>> Name: Swift(linux-x86_64)
>>> Failed: 0 test(s), Passed: 8233 test(s), Total: 8233 test(s)
>>> Name: Swift-Unit
>>> Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
>>> 
>>> Changes
>>> 
>>> Commit 41eb798f035aff1e705ec6d33a1f0ab2174fd978 by jordan_rose:
>>> [ClangImporter] Predefine __swift__ in imported (Obj)C code. (#4510)
>>> 
>>> edit: test/ClangModules/Inputs/custom-modules/module.map
>>> edit: include/swift/Basic/Version.h
>>> add: test/ClangModules/Inputs/custom-modules/PredefinedMacros.h
>>> edit: lib/ClangImporter/ClangImporter.cpp
>>> add: test/ClangModules/predefined_macros.swift
>>> edit: lib/Basic/Version.cpp
>>> 
>>> Commit 11999525bf57a87b818366438d6c8b68e886e3ae by jacob:
>>> [QoI] diagnose initializers written as typed patterns (SR-1461)
>>> 
>>> add: test/Parse/diagnose_initializer_as_typed_pattern.swift
>>> edit: lib/Parse/ParsePattern.cpp
>>> edit: include/swift/AST/DiagnosticsParse.def
>>> 
>>> Commit 2c998bda9c65343df0e1679b33f64f33af9725db by jacob:
>>> [QoI] fix diagnosis of non-Optional enum used in optional pattern
>>> 
>>> edit: lib/Sema/TypeCheckPattern.cpp
>>> edit: test/SILGen/statements.swift
>>> edit: test/stmt/if_while_var.swift
>>> 
>>> Commit fd8f6f537d223ad3ae5b588a1da47780a307d2c6 by xiaodi.wu:
>>> [Swift 3.0.1] Fix decimal
>>> 
>>> edit: stdlib/public/SDK/Foundation/Decimal.swift
>>> edit: test/Interpreter/SDK/NSDecimal.swift
>>> 
>>> Commit 29153b5bdf48d1bdd33c346bab87f49b1fa144ca by xiaodi.wu:
>>> Fix-up (line ending)
>>> 
>>> edit: test/Interpreter/SDK/NSDecimal.swift
>>> 
>>> 
>> 
> 

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


Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread David P Grove via swift-dev
Mishal,

What is the most reliable way to get the output of a .log file for a
failed test to be visible in the Jenkins console log?  Do I need to try to
add a hook to the autotools testing rules to cat a failed log file, or is
there some other mechanism available to us?

--dave




From:   Jordan Rose via swift-dev 
To: mishal_shah 
Cc: Jacob Bandes-Storch , swift-dev
, Xiaodi Wu 
Date:   08/31/2016 01:16 PM
Subject:Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift
Incremental RA - Ubuntu 14.04 (swift 3.0) #177
Sent by:swift-dev-boun...@swift.org



…but the smoke tests are still failing.

https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/925/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/926/
https://ci.swift.org/job/swift-PR-Linux-smoke-test/927/

(923 passed, for some reason.)


  On Aug 30, 2016, at 11:55, mishal_shah  wrote:

  Lib dispatch test failed, however next build passed (
  
https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/
  )

  

  Testsuite summary for libkqueue 2.0.4
  

  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  Thanks,
  Mishal Shah
On Aug 30, 2016, at 11:31 AM, Jordan Rose <
jordan_r...@apple.com> wrote:

I'm seeing this on all the Linux smoke tests right now. :-( Any
ideas, Mishal? Should we just try wiping the workspace?

Jordan


  On Aug 29, 2016, at 23:34, Jacob Bandes-Storch <
  ja...@bandes-storch.net> wrote:

  Not really sure what's going on here. The only failure I
  see is this, but I don't know what actually failed:

  make[3]: *** [test-suite.log] Error 1 make[3]: Leaving
  directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make[1]: *** [check-am] Error 2 make[1]: Leaving directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make: *** [check-recursive] Error
  1 
/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
 fatal error: command terminated with a non-zero exit status 2,
  aborting 
/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
 fatal error: command terminated with a non-zero exit status 1, aborting


  On Mon, Aug 29, 2016 at 11:18 PM, 
  wrote:
[FAILURE]
oss-swift-3.0-incremental-RA-linux-ubuntu-14_04 [#177]

 
  Build URL:   
https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/ 

 
   Project:oss-swift-3.0-incremental-RA-linux-ubuntu-14_04  
 

 
Date ofMon, 29 Aug 2016 23:06:18 -0700  
 
build:  
 

 
 Build 11 min   
 
   duration:
 

 

Tests:



 Name: Swift(linux-x86_64)  
 Failed: 0 test(s), Passed: 8233 test(s), Total: 8233 test(s)   


 

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread mishal_shah via swift-dev
Hi David, 

Does the tests provide xml output?

Thanks, 
Mishal Shah
> On Aug 31, 2016, at 10:23 AM, David P Grove  wrote:
> 
> Mishal,
> 
> What is the most reliable way to get the output of a .log file for a failed 
> test to be visible in the Jenkins console log? Do I need to try to add a hook 
> to the autotools testing rules to cat a failed log file, or is there some 
> other mechanism available to us?
> 
> --dave
> 
> 
> Jordan Rose via swift-dev ---08/31/2016 01:16:08 PM---…but the 
> smoke tests are still failing. 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/ 
> 
> 
> From:  Jordan Rose via swift-dev  >
> To:  mishal_shah mailto:mishal_s...@apple.com>>
> Cc:  Jacob Bandes-Storch  >, swift-dev  >, Xiaodi Wu  >
> Date:  08/31/2016 01:16 PM
> Subject:  Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift 
> Incremental RA - Ubuntu 14.04 (swift 3.0) #177
> Sent by:  swift-dev-boun...@swift.org 
> 
> 
> 
> …but the smoke tests are still failing.
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/925/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/926/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/927/ 
> 
> 
> (923 passed, for some reason.)
> 
> On Aug 30, 2016, at 11:55, mishal_shah  > wrote:
> 
> Lib dispatch test failed, however next build passed 
> (https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/
>  
> )
> 
> 
> Testsuite summary for libkqueue 2.0.4
> 
> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> 
> Thanks,
> Mishal Shah
> On Aug 30, 2016, at 11:31 AM, Jordan Rose  > wrote:
> 
> I'm seeing this on all the Linux smoke tests right now. :-( Any ideas, 
> Mishal? Should we just try wiping the workspace?
> 
> Jordan
> 
> On Aug 29, 2016, at 23:34, Jacob Bandes-Storch  > wrote:
> 
> Not really sure what's going on here. The only failure I see is this, but I 
> don't know what actually failed:
> 
> make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>  make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>  make[1]: *** [check-am] Error 2 make[1]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>  make: *** [check-recursive] Error 1 
> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>  fatal error: command terminated with a non-zero exit status 2, aborting 
> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>  fatal error: command terminated with a non-zero exit status 1, aborting 
> 
> 
> On Mon, Aug 29, 2016 at 11:18 PM,  > wrote:
> [FAILURE] oss-swift-3.0-incremental-RA-linux-ubuntu-14_04 [#177]
> Build URL:
> https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/ 
> 
> Project:
> oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
> Date of build:
> Mon, 29 Aug 2016 23:06:18 -0700
> Build duration:
> 11 min
> Tests: 
> 
> Name: Swift(linux-x86_64)
> Failed: 0 test(s), Passed: 8233 test(s), Total: 8233 test(s)
> 
> Name: Swift-Unit
> Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
> 
> Changes
> Commit 41eb798f035aff1e705ec6d33a1f0ab2174fd978 by jordan_rose:
> [ClangImporter] Predefine __swift__ in imported (Obj)C code. (#4510)
> 
> edit: test/ClangModules/Inputs/custom-modules/module.map
> edit: include/swift/Basic/Version.h
> add: test/ClangModules/Inputs/custom-modules/PredefinedMacros.h
> edit: lib/ClangImporter/ClangImporter.cpp
> add: test/ClangModules/predefined_macros.swift
> edit: lib/Basic/Version.cpp
> Commit 11999525bf57a87b818366438d6c8b68e886e3ae by jacob:
> [QoI] diagnose initializers written as typed pa

Re: [swift-dev] [SourceKit] Include sourcekitd.h in distributed toolchain

2016-08-31 Thread Argyrios Kyrtzidis via swift-dev

> On Aug 12, 2016, at 7:14 AM, Ryan Lovelett  wrote:
> 
>> The header is not currently bundled with Xcode because it is not
>> considered a supported stable API.
>> The toolchain snapshots from swift.org do not make any promises about
>> stable APIs so we include it with those.
> 
> Thank you for the response. It seems that you do a lot of the
> management/development of the SourceKit tool. Obviously you are way more
> knowledgeable than me about this.
> 
> Forgive the impertinence, but _why_ is the API not considered supported
> or stable? It is obvious Xcode makes use of it and I think Xcode is
> considered a stable product? Enough of that though.

There is a significant difference between using Xcode as a product that builds 
your project and using frameworks and headers contained inside the Xcode.app 
bundle to link with your project.
With ‘not supported’ I mean that, unless stated otherwise, frameworks contained 
inside the Xcode.app bundle are considered internal implementation details and 
we reserve the right to completely change them between Xcode versions (the ABI 
may change or the framework eliminated entirely, etc.); even though such 
changes may not have any observable changes for _using_ Xcode.app.

> 
> The far more important question is what can I do to change this
> position? Even more important is there anything that I can do to change
> the stance before Swift 3.0 is shipped?

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


[swift-dev] compile sourcekit for ios

2016-08-31 Thread Philipp Seibel via swift-dev
Hi,


I’m currently investigating if it is possible to compile sourcekit for ios. Has 
anyone information how to achieve this? I tried to compile swift via the 
build-scipt without success.


Thanks,
Philipp


Sent with Unibox


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


Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread David P Grove via swift-dev
No, no xml output.

--dave



From:   mishal_shah 
To: David P Grove/Watson/IBM@IBMUS
Cc: Jordan Rose , Jacob Bandes-Storch
, swift-dev ,
Xiaodi Wu 
Date:   08/31/2016 01:40 PM
Subject:Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift
Incremental RA - Ubuntu 14.04 (swift 3.0) #177
Sent by:mishal_s...@apple.com



Hi David,

Does the tests provide xml output?

Thanks,
Mishal Shah
  On Aug 31, 2016, at 10:23 AM, David P Grove 
  wrote:



  Mishal,

  What is the most reliable way to get the output of a .log file for a
  failed test to be visible in the Jenkins console log? Do I need to
  try to add a hook to the autotools testing rules to cat a failed log
  file, or is there some other mechanism available to us?

  --dave


  Jordan Rose via swift-dev ---08/31/2016 01:16:08
  PM---…but the smoke tests are still failing.
  https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/

  From:  Jordan Rose via swift-dev 
  To:  mishal_shah 
  Cc:  Jacob Bandes-Storch , swift-dev <
  swift-dev@swift.org>, Xiaodi Wu 
  Date:  08/31/2016 01:16 PM
  Subject:  Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift
  Incremental RA - Ubuntu 14.04 (swift 3.0) #177
  Sent by:  swift-dev-boun...@swift.org





  …but the smoke tests are still failing.

  https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/
  https://ci.swift.org/job/swift-PR-Linux-smoke-test/925/
  https://ci.swift.org/job/swift-PR-Linux-smoke-test/926/
  https://ci.swift.org/job/swift-PR-Linux-smoke-test/927/

  (923 passed, for some reason.)

  On Aug 30, 2016, at 11:55, mishal_shah <
  mishal_s...@apple.com> wrote:

  Lib dispatch test failed, however next build passed (
  
https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/
  )

  


  Testsuite summary for libkqueue 2.0.4
  


  # TOTAL: 1
  # PASS: 0
  # SKIP: 0
  # XFAIL: 0
  # FAIL: 1
  # XPASS: 0
  # ERROR: 0

  Thanks,
  Mishal Shah
  On Aug 30, 2016, at 11:31 AM, Jordan Rose <
  jordan_r...@apple.com> wrote:

  I'm seeing this on all the Linux smoke tests
  right now. :-( Any ideas, Mishal? Should we
  just try wiping the workspace?

  Jordan

  On Aug 29, 2016, at 23:34, Jacob
  Bandes-Storch <
  ja...@bandes-storch.net> wrote:

  Not really sure what's going on
  here. The only failure I see is
  this, but I don't know what
  actually failed:

  make[3]: *** [test-suite.log]
  Error 1 make[3]: Leaving
  directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make[1]: *** [check-am] Error 2 make[1]: Leaving directory
  
`/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
 make: *** [check-recursive] Error 1 
/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
 fatal error: command terminated with a non-zero exit status 2,
  aborting 
/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
 fatal error: command terminated with a non-zero exit status 1, aborting



  On Mon, Aug 29, 2016 at 11:18 PM,
   wrote:
[FAILURE]

oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
 [#177]
   

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift 3.0) #177

2016-08-31 Thread mishal_shah via swift-dev
If xml output is not supported, then I would recommend printing out failure 
logs into the console (stdout).

Thanks,
Mishal Shah
> On Aug 31, 2016, at 12:42 PM, David P Grove  wrote:
> 
> No, no xml output. 
> 
> --dave 
> 
> mishal_shah ---08/31/2016 01:40:33 PM---Hi David, Does the tests 
> provide xml output?
> 
> From: mishal_shah 
> To: David P Grove/Watson/IBM@IBMUS
> Cc: Jordan Rose , Jacob Bandes-Storch 
> , swift-dev , Xiaodi Wu 
> 
> Date: 08/31/2016 01:40 PM
> Subject: Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental 
> RA - Ubuntu 14.04 (swift 3.0) #177
> Sent by: mishal_s...@apple.com
> 
> 
> 
> 
> Hi David, 
> 
> Does the tests provide xml output?
> 
> Thanks, 
> Mishal Shah
> On Aug 31, 2016, at 10:23 AM, David P Grove  > wrote:
> Mishal,
> 
> What is the most reliable way to get the output of a .log file for a failed 
> test to be visible in the Jenkins console log? Do I need to try to add a hook 
> to the autotools testing rules to cat a failed log file, or is there some 
> other mechanism available to us?
> 
> --dave
> 
> 
> Jordan Rose via swift-dev ---08/31/2016 01:16:08 PM---…but the 
> smoke tests are still failing. 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/ 
> 
> 
> From: Jordan Rose via swift-dev  >
> To: mishal_shah mailto:mishal_s...@apple.com>>
> Cc: Jacob Bandes-Storch  >, swift-dev  >, Xiaodi Wu  >
> Date: 08/31/2016 01:16 PM
> Subject: Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental 
> RA - Ubuntu 14.04 (swift 3.0) #177
> Sent by: swift-dev-boun...@swift.org 
> 
> 
> 
> 
> …but the smoke tests are still failing.
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/924/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/925/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/926/ 
> 
> https://ci.swift.org/job/swift-PR-Linux-smoke-test/927/ 
> 
> 
> (923 passed, for some reason.)
> On Aug 30, 2016, at 11:55, mishal_shah  > wrote:
> 
> Lib dispatch test failed, however next build passed 
> (https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/178/
>  
> )
> 
> 
> Testsuite summary for libkqueue 2.0.4
> 
> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> 
> Thanks,
> Mishal Shah
> On Aug 30, 2016, at 11:31 AM, Jordan Rose  > wrote:
> 
> I'm seeing this on all the Linux smoke tests right now. :-( Any ideas, 
> Mishal? Should we just try wiping the workspace?
> 
> Jordan
> On Aug 29, 2016, at 23:34, Jacob Bandes-Storch  > wrote:
> 
> Not really sure what's going on here. The only failure I see is this, but I 
> don't know what actually failed:
> 
> make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>  make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>  make[1]: *** [check-am] Error 2 make[1]: Leaving directory 
> `/home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/libdispatch-linux-x86_64/libkqueue'
>  make: *** [check-recursive] Error 1 
> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>  fatal error: command terminated with a non-zero exit status 2, aborting 
> /home/buildnode/jenkins/workspace/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/swift/utils/build-script:
>  fatal error: command terminated with a non-zero exit status 1, aborting 
> 
> 
> On Mon, Aug 29, 2016 at 11:18 PM,  > wrote:
> [FAILURE] oss-swift-3.0-incremental-RA-linux-ubuntu-14_04 [#177]
> Build URL:
> https://ci.swift.org/job/oss-swift-3.0-incremental-RA-linux-ubuntu-14_04/177/ 
> 
> Project:
> oss-swift-3.0-incremental-RA-linux-ubuntu-14_04
> Date of build:
> Mon, 29 Aug 2016 23:06:18 -0700
> Build duration:
> 11 min
> Tests:
> 
> Name: Swift(linux-x86_64)
> Failed: 0 test(s), Passed: 

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

2016-08-31 Thread Anders Bertelrud via swift-dev
Looks unrelated to the checkins mentioned in this email:

Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_1' passed 
(0.0 seconds).
Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_2' started 
at 20:30:25.699
Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_2' passed 
(0.0 seconds).
Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_3' started 
at 20:30:25.699
Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_3' passed 
(0.0 seconds).
Test Suite 'TestNSHTTPURLResponse' passed at 20:30:25.699
 Executed 25 tests, with 0 failures (0 unexpected) in 0.003 (0.003) 
seconds
Test Suite 'TestURLSession' started at 20:30:25.699
Test Case 'TestURLSession.test_dataTaskWithURL' started at 20:30:25.699

Build timed out (after 45 minutes). Marking the build as failed.

Build was aborted


Anders

> On 2016-08-31, at 14.15, no-re...@swift.org wrote:
> 
> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#7230]
> 
> Build URL:
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/7230/ 
> 
> Project:  oss-swift-incremental-RA-linux-ubuntu-14_04
> Date of build:Wed, 31 Aug 2016 13:03:22 -0700
> Build duration:   1 hr 12 min
> Identified problems:
> 
> Timeout: This build was marked as FAIL because it timed out.
> Indication 1 
> 
> Tests: 
> 
> Name: Swift(linux-x86_64)
> Failed: 0 test(s), Passed: 8279 test(s), Total: 8279 test(s)
> Name: Swift-Unit
> Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
> 
> Changes
> 
> Commit 3fa09465c42941444c336acd68092362facd87a1 by nmaccharoli:
> [stdlib] Move empty check for string concatenation to front
> 
> edit: stdlib/public/core/String.swift
> 
> Commit 82b37b3e7fed122150dd602e29cae966cebf494d by anders:
> Check for loose source files in the `Tests` directory (it's a package
> 
> edit: Sources/PackageLoading/PackageBuilder.swift
> edit: Tests/PackageLoadingTests/ConventionTests.swift

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


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

2016-08-31 Thread Philippe Hausler via swift-dev
Those tests have been disabled by 
https://github.com/apple/swift-corelibs-foundation/commit/b98f8d67071b0af39f85c589dfd6cb54ff7c06cd

Sent from my iPhone

> On Aug 31, 2016, at 2:18 PM, Anders Bertelrud via swift-dev 
>  wrote:
> 
> Looks unrelated to the checkins mentioned in this email:
> 
> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_1' passed 
> (0.0 seconds).
> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_2' started 
> at 20:30:25.699
> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_2' passed 
> (0.0 seconds).
> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_3' started 
> at 20:30:25.699
> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_3' passed 
> (0.0 seconds).
> Test Suite 'TestNSHTTPURLResponse' passed at 20:30:25.699
>Executed 25 tests, with 0 failures (0 unexpected) in 0.003 (0.003) 
> seconds
> Test Suite 'TestURLSession' started at 20:30:25.699
> Test Case 'TestURLSession.test_dataTaskWithURL' started at 20:30:25.699
> 
> Build timed out (after 45 minutes). Marking the build as failed.
> 
> Build was aborted
> 
> 
> Anders
> 
>> On 2016-08-31, at 14.15, no-re...@swift.org wrote:
>> 
>> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#7230]
>> 
>> Build URL:   
>> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/7230/
>> Project: oss-swift-incremental-RA-linux-ubuntu-14_04
>> Date of build:   Wed, 31 Aug 2016 13:03:22 -0700
>> Build duration:  1 hr 12 min
>> Identified problems:
>> 
>> Timeout: This build was marked as FAIL because it timed out.
>> Indication 1
>> Tests: 
>> 
>> Name: Swift(linux-x86_64)
>> Failed: 0 test(s), Passed: 8279 test(s), Total: 8279 test(s)
>> Name: Swift-Unit
>> Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
>> 
>> Changes
>> 
>> Commit 3fa09465c42941444c336acd68092362facd87a1 by nmaccharoli:
>> [stdlib] Move empty check for string concatenation to front
>> 
>> edit: stdlib/public/core/String.swift
>> 
>> Commit 82b37b3e7fed122150dd602e29cae966cebf494d by anders:
>> Check for loose source files in the `Tests` directory (it's a package
>> 
>> edit: Sources/PackageLoading/PackageBuilder.swift
>> edit: Tests/PackageLoadingTests/ConventionTests.swift
> 
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev


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

2016-08-31 Thread Michael Gottesman via swift-dev
Why wasn't this caught by pull request testing?

Michael

> On Aug 31, 2016, at 3:56 PM, Philippe Hausler via swift-dev 
>  wrote:
> 
> Those tests have been disabled by 
> https://github.com/apple/swift-corelibs-foundation/commit/b98f8d67071b0af39f85c589dfd6cb54ff7c06cd
>  
> 
> Sent from my iPhone
> 
> On Aug 31, 2016, at 2:18 PM, Anders Bertelrud via swift-dev 
> mailto:swift-dev@swift.org>> wrote:
> 
>> Looks unrelated to the checkins mentioned in this email:
>> 
>> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_1' passed 
>> (0.0 seconds).
>> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_2' 
>> started at 20:30:25.699
>> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_2' passed 
>> (0.0 seconds).
>> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_3' 
>> started at 20:30:25.699
>> Test Case 'TestNSHTTPURLResponse.test_MIMETypeAndCharacterEncoding_3' passed 
>> (0.0 seconds).
>> Test Suite 'TestNSHTTPURLResponse' passed at 20:30:25.699
>>   Executed 25 tests, with 0 failures (0 unexpected) in 0.003 (0.003) 
>> seconds
>> Test Suite 'TestURLSession' started at 20:30:25.699
>> Test Case 'TestURLSession.test_dataTaskWithURL' started at 20:30:25.699
>> 
>> Build timed out (after 45 minutes). Marking the build as failed.
>> 
>> Build was aborted
>> 
>> 
>> Anders
>> 
>>> On 2016-08-31, at 14.15, no-re...@swift.org  
>>> wrote:
>>> 
>>> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#7230]
>>> 
>>> Build URL:  
>>> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/7230/ 
>>> 
>>> Project:oss-swift-incremental-RA-linux-ubuntu-14_04
>>> Date of build:  Wed, 31 Aug 2016 13:03:22 -0700
>>> Build duration: 1 hr 12 min
>>> Identified problems:
>>> 
>>> Timeout: This build was marked as FAIL because it timed out.
>>> Indication 1 
>>> 
>>> Tests: 
>>> 
>>> Name: Swift(linux-x86_64)
>>> Failed: 0 test(s), Passed: 8279 test(s), Total: 8279 test(s)
>>> Name: Swift-Unit
>>> Failed: 0 test(s), Passed: 230 test(s), Total: 230 test(s)
>>> 
>>> Changes
>>> 
>>> Commit 3fa09465c42941444c336acd68092362facd87a1 by nmaccharoli:
>>> [stdlib] Move empty check for string concatenation to front
>>> 
>>> edit: stdlib/public/core/String.swift
>>> 
>>> Commit 82b37b3e7fed122150dd602e29cae966cebf494d by anders:
>>> Check for loose source files in the `Tests` directory (it's a package
>>> 
>>> edit: Sources/PackageLoading/PackageBuilder.swift
>>> edit: Tests/PackageLoadingTests/ConventionTests.swift
>> 
>> ___
>> swift-dev mailing list
>> swift-dev@swift.org 
>> https://lists.swift.org/mailman/listinfo/swift-dev 
>> 
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

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