/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/ManifestParser/ManifestTests.swift:15:8: error: no such module 'XCTest'
import XCTest
On Feb 16, 2016, at 6:43 PM, no-reply@swift.org wrote:
On Tue, Feb 16, 2016 at 6:43 PM, Argyrios Kyrtzidis via swift-dev < swift-dev@swift.org> wrote:
Doesn’t look related to my change:
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/ManifestParser/ManifestTests.swift:15:8:
error: no such module 'XCTest' import XCTest
On Feb 16, 2016, at 6:43 PM, no-reply@swift.org wrote:
New issue found![FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10
[#2503]
Build URL: https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/2503/
Project: oss-swift-incremental-RA-linux-ubuntu-15_10
Date of build: Tue, 16 Feb 2016 20:36:22 -0600
Build duration: 7 min 30 secIdentified problems:
On Feb 16, 2016, at 6:46 PM, Dmitri Gribenko <gribozavr@gmail.com> wrote:
+ Daniel, Max
On Tue, Feb 16, 2016 at 6:43 PM, Argyrios Kyrtzidis via swift-dev <swift-dev@swift.org> wrote:
Doesn’t look related to my change:
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/ManifestParser/ManifestTests.swift:15:8: error: no such module 'XCTest'
import XCTest
On Feb 16, 2016, at 6:43 PM, no-reply@swift.org wrote:
Just tried to re-enable Foundation tests on the 25th snapshot, I still get this error.
Drew
···
On Feb 17, 2016, at 1:46 AM, Max Howell via swift-dev <swift-dev@swift.org> wrote:
Yes this is my fault. Almost fixed.
On Feb 16, 2016, at 6:46 PM, Dmitri Gribenko <gribozavr@gmail.com <mailto:gribozavr@gmail.com>> wrote:
+ Daniel, Max
On Tue, Feb 16, 2016 at 6:43 PM, Argyrios Kyrtzidis via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Doesn’t look related to my change:
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/ManifestParser/ManifestTests.swift:15:8: error: no such module 'XCTest'
import XCTest
On Feb 16, 2016, at 6:43 PM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
Just tried to re-enable Foundation tests on the 25th snapshot, I still get this error.
Well, CI is working here, so it *should* work let’s examine your environment. This is Ubuntu 15.10? How are you running the tests?
···
On Feb 17, 2016, at 1:46 AM, Max Howell via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Yes this is my fault. Almost fixed.
On Feb 16, 2016, at 6:46 PM, Dmitri Gribenko <gribozavr@gmail.com <mailto:gribozavr@gmail.com>> wrote:
+ Daniel, Max
On Tue, Feb 16, 2016 at 6:43 PM, Argyrios Kyrtzidis via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Doesn’t look related to my change:
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/ManifestParser/ManifestTests.swift:15:8: error: no such module 'XCTest'
import XCTest
On Feb 16, 2016, at 6:43 PM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
When building the Feb 8th snapshot from source on Linux x64, I see a new error:
TestFoundation/TestNSString.swift:13:8: error: no such module 'XCTest'
import XCTest
^
ninja: build stopped: subcommand failed.
./utils/build-script: command terminated with a non-zero exit status 1, aborting
./utils/build-script: using preset 'drew', which expands to ./utils/build-script --assertions --no-swift-stdlib-assertions --llbuild --swiftpm --xctest --build-subdir=buildbot_linux --lldb --release --test --validation-test --foundation --libdispatch -- --swift-enable-ast-verifier=0 --install-swift --install-lldb --install-llbuild --install-swiftpm --install-xctest --install-prefix=/usr '--swift-install-components=compiler;clang-builtin-headers;stdlib;sdk-overlay;license' --build-swift-static-stdlib=1 --build-swift-stdlib-unittest-extra=1 --skip-test-lldb=1 --test-installable-package=1 --install-destdir=/tmp/install --installable-package=/tmp/swift.tar.gz --install-foundation --reconfigure --install-libdispatch=1 --skip-test-libdispatch=1
./utils/build-script: command terminated with a non-zero exit status 1, aborting
I am currently working around by setting skip-test-foundation=1.
I assume there's a bug already filed on this?
Possibly related to use of libdispatch, which CI doesn't do yet.
I'm on Debian Jessie x64, but I don't think it's a distro issue, as this "used to work".
Using --skip-test-foundation=1 resolves the issue, I assume because this code is no longer compiled.
···
On Feb 29, 2016, at 12:11 PM, Max Howell <mxcl@me.com> wrote:
I asked about this on swift-dev on Feb 9th.
Just tried to re-enable Foundation tests on the 25th snapshot, I still get this error.
Well, CI is working here, so it *should* work let’s examine your environment. This is Ubuntu 15.10? How are you running the tests?
On Feb 17, 2016, at 1:46 AM, Max Howell via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Yes this is my fault. Almost fixed.
On Feb 16, 2016, at 6:46 PM, Dmitri Gribenko <gribozavr@gmail.com <mailto:gribozavr@gmail.com>> wrote:
+ Daniel, Max
On Tue, Feb 16, 2016 at 6:43 PM, Argyrios Kyrtzidis via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Doesn’t look related to my change:
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/ManifestParser/ManifestTests.swift:15:8: error: no such module 'XCTest'
import XCTest
On Feb 16, 2016, at 6:43 PM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
Still fresh on swift-DEVELOPMENT-SNAPSHOT-2016-03-16-a; disabling foundation tests and snoozing until the next snapshot
···
On Mar 1, 2016, at 4:02 AM, Drew Crawford <drew@sealedabstract.com> wrote:
From Feb 9th:
Hello,
When building the Feb 8th snapshot from source on Linux x64, I see a new error:
TestFoundation/TestNSString.swift:13:8: error: no such module 'XCTest'
import XCTest
^
ninja: build stopped: subcommand failed.
./utils/build-script: command terminated with a non-zero exit status 1, aborting
./utils/build-script: using preset 'drew', which expands to ./utils/build-script --assertions --no-swift-stdlib-assertions --llbuild --swiftpm --xctest --build-subdir=buildbot_linux --lldb --release --test --validation-test --foundation --libdispatch -- --swift-enable-ast-verifier=0 --install-swift --install-lldb --install-llbuild --install-swiftpm --install-xctest --install-prefix=/usr '--swift-install-components=compiler;clang-builtin-headers;stdlib;sdk-overlay;license' --build-swift-static-stdlib=1 --build-swift-stdlib-unittest-extra=1 --skip-test-lldb=1 --test-installable-package=1 --install-destdir=/tmp/install --installable-package=/tmp/swift.tar.gz --install-foundation --reconfigure --install-libdispatch=1 --skip-test-libdispatch=1
./utils/build-script: command terminated with a non-zero exit status 1, aborting
I am currently working around by setting skip-test-foundation=1.
I assume there's a bug already filed on this?
Possibly related to use of libdispatch, which CI doesn't do yet.
I'm on Debian Jessie x64, but I don't think it's a distro issue, as this "used to work".
Using --skip-test-foundation=1 resolves the issue, I assume because this code is no longer compiled.
On Feb 29, 2016, at 12:11 PM, Max Howell <mxcl@me.com <mailto:mxcl@me.com>> wrote:
I asked about this on swift-dev on Feb 9th.
Just tried to re-enable Foundation tests on the 25th snapshot, I still get this error.
Well, CI is working here, so it *should* work let’s examine your environment. This is Ubuntu 15.10? How are you running the tests?
On Feb 17, 2016, at 1:46 AM, Max Howell via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Yes this is my fault. Almost fixed.
On Feb 16, 2016, at 6:46 PM, Dmitri Gribenko <gribozavr@gmail.com <mailto:gribozavr@gmail.com>> wrote:
+ Daniel, Max
On Tue, Feb 16, 2016 at 6:43 PM, Argyrios Kyrtzidis via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Doesn’t look related to my change:
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/ManifestParser/ManifestTests.swift:15:8: error: no such module 'XCTest'
import XCTest
On Feb 16, 2016, at 6:43 PM, no-reply@swift.org <mailto:no-reply@swift.org> wrote: