[swift-dev] Failure: Swift master branch build failing on x86 (Ubuntu 16.04).
Atul Sowani
sowani at gmail.com
Tue Oct 10 01:57:50 CDT 2017
I tried the same build command I found in one of passing CI jobs for Ubuntu
16.04 (e.g.
https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_04/943/consoleFull
):
utils/build-script --assertions --release --test --validation-test
--lit-args=-v --build-subdir=buildbot_incremental --llbuild --swiftpm
--xctest --foundation --libdispatch -- --build-ninja --reconfigure --jobs 16
This seems to be passing (at least building swift) on my local x86_64
machine. There are few test failures but I am not worried about them at
this point. I tried this same command on ppc64le and got into trouble with
llvm/clang. The clang crashed while processing
swift/stdlib/public/runtime/Casting.cpp somewhere inside
swift::swift_getTypeName - so it looks like (1) I should not use Makefile
build and (2) investigate more on the CLang crash.
Thanks!
On Mon, Oct 9, 2017 at 11:19 PM, Jordan Rose <jordan_rose at apple.com> wrote:
> I will note that the Makefile build is not something we test. What happens
> if you drop -m from your build command, to use Ninja instead?
>
> Jordan
>
>
> On Oct 8, 2017, at 22:36, Slava Pestov via swift-dev <swift-dev at swift.org>
> wrote:
>
> Hi Atul,
>
> The master branch is tested in CI, so any build failures are likely due to
> configuration problems on your end. While testing the swift-4.0-branch
> would provide an interesting data point, I would not expect it to work if
> building master fails.
>
> Slava
>
> On Oct 8, 2017, at 10:35 PM, Atul Sowani via swift-dev <
> swift-dev at swift.org> wrote:
>
> I still have no luck building swift on x86 using the master branch. Is it
> recommended to use the master branch at all (considering a lot of fixes
> would be coming in) or is it desirable to use 4.0 branch instead as a
> general rule?
>
> Thanks,
> Atul.
>
> On Fri, Oct 6, 2017 at 7:03 PM, Atul Sowani via swift-dev <
> swift-dev at swift.org> wrote:
>
>> Thanks Alex! I used the clean/reset command and then tried rebuilding it,
>> but got the very same error. I am using master branch, latest
>> (top-of-the-tree) version:
>>
>> git clone https://github.com/apple/swift.git
>> ./swift/utils/update-checkout --clone
>> cd swift
>> utils/build-script -c -m -R --verbose-build
>>
>> Hope this is correct.
>>
>> Thanks,
>> Atul.
>>
>> On Fri, Oct 6, 2017 at 5:51 PM, Alex Blewitt <alblue at apple.com> wrote:
>>
>>>
>>>
>>> > On 6 Oct 2017, at 12:42, Atul Sowani via swift-dev <
>>> swift-dev at swift.org> wrote:
>>> >
>>> > Hi,
>>> >
>>> > Swift "master" branch is failing to build on x86 running Ubuntu 16,04
>>> with following error.
>>>
>>> Most of the recent builds appear to be working:
>>>
>>> https://ci.swift.org/view/swift-master-next/job/oss-swift-in
>>> cremental-RA-linux-ubuntu-16_04-master-next/
>>>
>>> > I am using following build command from inside swift-source/swift
>>> directory:
>>> > utils/build-script -c -m -R --verbose-build
>>>
>>> What version of the 'swift' project do you have checked out? Have you
>>> done a clean/reset to make sure those aren't issues at the moment?
>>>
>>> You can run swift/utils/update-checkout --clean --reset-to-remote
>>> --scheme master (which will get rid of any cruft if you haven't got
>>> anything you need to keep) and then re-run the build to see if that
>>> resolves the errors.
>>>
>>> Alex
>>>
>>
>>
>> _______________________________________________
>> swift-dev mailing list
>> swift-dev at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-dev
>>
>>
> _______________________________________________
> swift-dev mailing list
> swift-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
>
>
> _______________________________________________
> swift-dev mailing list
> swift-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-dev/attachments/20171010/43e44545/attachment.html>
More information about the swift-dev
mailing list