With autotools, the first time libdispatch was built (for SourceKit), it
just did the C build of libdispatch. That had to be blown away and rebuilt
a second time later (once swiftc, etc was available) so that we could build
libdispatch.so with the Swift overlay built into it.
Did you manage to c
swift-dev-boun...@swift.org wrote on 05/17/2017 02:04:23 PM:
>
> Failure in dispatch-starfish. This test looks timing-sensitive.
> Boris, is this unlikely to be related to your changes? Does anyone
> familiar with dispatch have suggestions, such as increasing the
> latency threshold?
>
> [BEGIN]
t by:mgottes...@apple.com
On Feb 17, 2017, at 11:30 AM, David P Grove via swift-dev <
swift-dev@swift.org> wrote:
swift-dev-boun...@swift.org wrote on 02/16/2017 09:48:28 PM:
>
> I was curious about the overhead of ARC and started profil
swift-dev-boun...@swift.org wrote on 02/16/2017 09:48:28 PM:
>
> I was curious about the overhead of ARC and started profiling some
> benchmarks found in the Computer Language Benchmark Game (http://
> benchmarksgame.alioth.debian.org/u64q/measurements.php?lang=swift).
> So far, it seems that AR
, 2017, at 10:39 AM, Ted kremenek via swift-dev <
swift-dev@swift.org> wrote:
[ + Daniel, Rick, concerning SwiftPM piece ]
On Jan 27, 2017, at 10:15 AM, David P Grove via swift-dev <
swift-dev@swift.org> wrote:
Hi,
The libdispa
Hi,
The libdispatch Linux PR testing (
https://ci.swift.org/view/Pull%20Request/job/swift-corelibs-libdispatch-PR-Linux/
) has been failing due to a timeout in the swiftpm
BuildToolTests.testBuildAndClean test for several weeks (independent of the
actual change being tested by the PR tes
Normally when we build dispatch, we use the version of clang that is being
built along with the swift compiler (not the clang on the build machine).
This is done in build-script-impl by setting CC, CXX, etc before invoking
configure.
with_pushd "${LIBDISPATCH_BUILD_DIR}" \
> From: John McCall via swift-dev
> To: Jiho Choi
> Cc: swift-dev@swift.org
> Date: 11/30/2016 12:41 PM
> Subject: Re: [swift-dev] Questions about ARC
> Sent by: swift-dev-boun...@swift.org
>
> On Nov 30, 2016, at 8:33 AM, Jiho Choi via swift-dev > wrote:
> >
> >
> 4. Lastly, is there a way to
I think the root problem is that some of the dispatch tests, including this
one, are trying to test that timers/events happen within a "reasonable"
interval of time from when they are supposed to. If deadlines are missed
too badly, then the test is marked as failing.
If we completely disabled al
Sorry,
I think the fix for this is a one-time forced update (or removal to
get a clean checkout) of libdispatch on the build machines.
The problem is that libpwq has config.h.in checked into git. That
file really shouldn't be in source control because it is generated by
autotools
ib + Dispatch overlay)
3. Foundation
Otherwise we need to build Swift, then build libdispatch, then go
back to "Swift" to build the overlay, and only finally get to
Foundation.
Jordan
On Sep 23, 2016, at 14:32, David P Grove via swif
(compiler + stdlib + Dispatch overlay)
3. Foundation
Otherwise we need to build Swift, then build libdispatch, then go back to
"Swift" to build the overlay, and only finally get to Foundation.
Jordan
On Sep 23, 2016, at 14:32, David P Grove via swift-dev <
swi
On Sep 21, 2016, at 6:59 AM, David P Grove
via swift-dev wrote:
I don't know how the PR jobs are setup, but
the error suggests that they are trying to
I don't know how the PR jobs are setup, but the error suggests that they
are trying to reuse too much of the workspace of previous runs.
:0: error: module file was created by an older version of the
compiler; rebuild 'Dispatch' and try
again:
/home/buildnode/jenkins/workspace/swift-package-manag
swift-dev-boun...@swift.org wrote on 09/14/2016 01:34:10 PM:
>
> I'm trying to build Swift 3 for Fedora 24. Fedora doesn't come with
> libkqueue so I built and installed that manually into
> /usr/(include|lib). Building libdispatch as part of the build script
> fails when trying to build the tes
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
Incre
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:
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
I've never seen this test fail before. We haven't changed the kqueue git
submodule version since July 20. It looks like the next 20 runs of this CI
build didn't hit this test failure either.
I took a quick scan of the kqueue tests and like some of the other
libdispatch test cases, the kqueue t
Hi Drew,
Pick up this: https://github.com/apple/swift/pull/3835
It adds -fblocks to C language options to the ClangImporter on Linux.
--dave
swift-dev-boun...@swift.org wrote on 08/14/2016 02:14:13 AM:
>
> When attempting to build Swift Preview 5 on Linux, I get this error:
>
>
Dmitri Gribenko wrote on 06/02/2016 06:19:33 PM:
>
> Could you check if there are multiple definitions of off_t or mode_t
> in different headers guarded by macros? Something like this,
> duplicated across several headers:
>
> #if !defined(_OFF_T_DEFINED)
> typedef __off_t off_t;
> #define _OFF_T_
As part of helping to resolve old libdispatch pull requests, I have run
into a problem with the GLibc module map on Linux that I need help
understanding and fixing.
The symptom I am trying to resolve is that somewhere between the March 16
and March 24 Swift development snapshots, the Dispatch ov
22 matches
Mail list logo
