I need to push corelibs changes in today but I’m running into problems testing the full Swift toolchain on linux. build-toolchain stops after attempting to run swiftpm tests and hitting the failure shown below.
Anyone else seeing issues running build-toolchain?
As of:
commit cb0b4588a6a8bf80dc0efa52857df62f361e81d5 (HEAD -> master, origin/master, origin/HEAD)
Merge: 9bb96ee 77ef84b
Author: Daniel Dunbar <daniel_dunbar@apple.com>
Merge branch 'more-convention-tests' of GitHub - aciidb0mb3r/swift-package-manager: The Package Manager for the Swift Programming Language
···
Date: Wed Jul 27 08:47:50 2016
---
Test Case 'ClangModulesTestCase.testCUsingCDep2' started at 10:23:02.222
Building Debug
**** FAILURE EXECUTING SUBPROCESS ****
command: /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build --chdir /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar --configuration debug
SWIFT_EXEC: nil
output: Cloning /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Foo
HEAD is now at f42e04e msg
Resolved version: 1.2.3
Compile Foo Foo.c
Linking Foo
Compile SeaLover Sea.c
Compile Swift Module 'SwiftExec' (1 sources)
/tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar/Sources/SeaLover/Sea.c:1:10: fatal error: could not acquire lock file for module 'Foo'
#include <Foo/Foo.h>
^
1 error generated.
<unknown>:0: error: build had 1 command failures
swift-build: error: exit(1): /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build-tool -f /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar/.build/debug.yaml
/home/atrick/s/swiftpm/Tests/Functional/ClangModuleTests.swift:96: error: ClangModulesTestCase.testCUsingCDep2 : failed - `swift build -c Debug' failed:
exit(1): /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build --chdir /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar --configuration debug
--- bootstrap: error: tests failed with exit status 1
./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting
ddunbar
(Daniel Dunbar)
2
I don't run build toolchain myself (I have my own scripts for assembling one), but I run `build-script -R --llbuild --foundation --xctest -t` without issue.
+Jordan, Ben for what situations could cause the actual error we are hitting there.
- Daniel
···
On Jul 28, 2016, at 9:27 AM, Andrew Trick <atrick@apple.com> wrote:
I need to push corelibs changes in today but I’m running into problems testing the full Swift toolchain on linux. build-toolchain stops after attempting to run swiftpm tests and hitting the failure shown below.
Anyone else seeing issues running build-toolchain?
As of:
commit cb0b4588a6a8bf80dc0efa52857df62f361e81d5 (HEAD -> master, origin/master, origin/HEAD)
Merge: 9bb96ee 77ef84b
Author: Daniel Dunbar <daniel_dunbar@apple.com>
Date: Wed Jul 27 08:47:50 2016
Merge branch 'more-convention-tests' of GitHub - aciidb0mb3r/swift-package-manager: The Package Manager for the Swift Programming Language
---
Test Case 'ClangModulesTestCase.testCUsingCDep2' started at 10:23:02.222
Building Debug
**** FAILURE EXECUTING SUBPROCESS ****
command: /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build --chdir /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar --configuration debug
SWIFT_EXEC: nil
output: Cloning /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Foo
HEAD is now at f42e04e msg
Resolved version: 1.2.3
Compile Foo Foo.c
Linking Foo
Compile SeaLover Sea.c
Compile Swift Module 'SwiftExec' (1 sources)
/tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar/Sources/SeaLover/Sea.c:1:10: fatal error: could not acquire lock file for module 'Foo'
#include <Foo/Foo.h>
^
1 error generated.
<unknown>:0: error: build had 1 command failures
swift-build: error: exit(1): /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build-tool -f /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar/.build/debug.yaml
/home/atrick/s/swiftpm/Tests/Functional/ClangModuleTests.swift:96: error: ClangModulesTestCase.testCUsingCDep2 : failed - `swift build -c Debug' failed:
exit(1): /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build --chdir /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar --configuration debug
--- bootstrap: error: tests failed with exit status 1
./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting
blangmuir
(Ben Langmuir)
3
That error indicates some kind of filesystem issue in the module cache directory - no permissions, out of space, the directory has been removed by some other process, etc. +Bruno who was looking at making this error more specific.
Ben
···
On Jul 28, 2016, at 9:29 AM, Daniel Dunbar <daniel_dunbar@apple.com> wrote:
I don't run build toolchain myself (I have my own scripts for assembling one), but I run `build-script -R --llbuild --foundation --xctest -t` without issue.
+Jordan, Ben for what situations could cause the actual error we are hitting there.
- Daniel
On Jul 28, 2016, at 9:27 AM, Andrew Trick <atrick@apple.com> wrote:
I need to push corelibs changes in today but I’m running into problems testing the full Swift toolchain on linux. build-toolchain stops after attempting to run swiftpm tests and hitting the failure shown below.
Anyone else seeing issues running build-toolchain?
As of:
commit cb0b4588a6a8bf80dc0efa52857df62f361e81d5 (HEAD -> master, origin/master, origin/HEAD)
Merge: 9bb96ee 77ef84b
Author: Daniel Dunbar <daniel_dunbar@apple.com>
Date: Wed Jul 27 08:47:50 2016
Merge branch 'more-convention-tests' of GitHub - aciidb0mb3r/swift-package-manager: The Package Manager for the Swift Programming Language
---
Test Case 'ClangModulesTestCase.testCUsingCDep2' started at 10:23:02.222
Building Debug
**** FAILURE EXECUTING SUBPROCESS ****
command: /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build --chdir /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar --configuration debug
SWIFT_EXEC: nil
output: Cloning /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Foo
HEAD is now at f42e04e msg
Resolved version: 1.2.3
Compile Foo Foo.c
Linking Foo
Compile SeaLover Sea.c
Compile Swift Module 'SwiftExec' (1 sources)
/tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar/Sources/SeaLover/Sea.c:1:10: fatal error: could not acquire lock file for module 'Foo'
#include <Foo/Foo.h>
^
1 error generated.
<unknown>:0: error: build had 1 command failures
swift-build: error: exit(1): /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build-tool -f /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar/.build/debug.yaml
/home/atrick/s/swiftpm/Tests/Functional/ClangModuleTests.swift:96: error: ClangModulesTestCase.testCUsingCDep2 : failed - `swift build -c Debug' failed:
exit(1): /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build --chdir /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar --configuration debug
--- bootstrap: error: tests failed with exit status 1
./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting
Thanks Ben.
Daniel’s command works for me:
build-script -R --llbuild --foundation --xctest -t
But doesn’t build all the projects.
-Andy
···
On Jul 28, 2016, at 9:39 AM, Ben Langmuir <blangmuir@apple.com> wrote:
That error indicates some kind of filesystem issue in the module cache directory - no permissions, out of space, the directory has been removed by some other process, etc. +Bruno who was looking at making this error more specific.
Ben
On Jul 28, 2016, at 9:29 AM, Daniel Dunbar <daniel_dunbar@apple.com> wrote:
I don't run build toolchain myself (I have my own scripts for assembling one), but I run `build-script -R --llbuild --foundation --xctest -t` without issue.
+Jordan, Ben for what situations could cause the actual error we are hitting there.
- Daniel
On Jul 28, 2016, at 9:27 AM, Andrew Trick <atrick@apple.com> wrote:
I need to push corelibs changes in today but I’m running into problems testing the full Swift toolchain on linux. build-toolchain stops after attempting to run swiftpm tests and hitting the failure shown below.
Anyone else seeing issues running build-toolchain?
As of:
commit cb0b4588a6a8bf80dc0efa52857df62f361e81d5 (HEAD -> master, origin/master, origin/HEAD)
Merge: 9bb96ee 77ef84b
Author: Daniel Dunbar <daniel_dunbar@apple.com>
Date: Wed Jul 27 08:47:50 2016
Merge branch 'more-convention-tests' of GitHub - aciidb0mb3r/swift-package-manager: The Package Manager for the Swift Programming Language
---
Test Case 'ClangModulesTestCase.testCUsingCDep2' started at 10:23:02.222
Building Debug
**** FAILURE EXECUTING SUBPROCESS ****
command: /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build --chdir /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar --configuration debug
SWIFT_EXEC: nil
output: Cloning /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Foo
HEAD is now at f42e04e msg
Resolved version: 1.2.3
Compile Foo Foo.c
Linking Foo
Compile SeaLover Sea.c
Compile Swift Module 'SwiftExec' (1 sources)
/tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar/Sources/SeaLover/Sea.c:1:10: fatal error: could not acquire lock file for module 'Foo'
#include <Foo/Foo.h>
^
1 error generated.
<unknown>:0: error: build had 1 command failures
swift-build: error: exit(1): /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build-tool -f /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar/.build/debug.yaml
/home/atrick/s/swiftpm/Tests/Functional/ClangModuleTests.swift:96: error: ClangModulesTestCase.testCUsingCDep2 : failed - `swift build -c Debug' failed:
exit(1): /home/atrick/s/build/buildbot_linux/swiftpm-linux-x86_64/debug/swift-build --chdir /tmp/DependencyResolution_External_CUsingCDep2.5dXdqO/Bar --configuration debug
--- bootstrap: error: tests failed with exit status 1
./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting