Github user navsan commented on the issue:
https://github.com/apache/incubator-quickstep/pull/101
The compiler is probably running out of memory. Can you try turning down
the level of parallelism?
On Mon, Oct 3, 2016, 08:48 Saket Saurabh <[email protected]> wrote:
> It is strange that only one of the Travis build tasks for [clang++
> compiler, build=release and vector_copy_ellision_level=selection] is
> repeatedly failing due to a compiler error. (Reproduced below) .
>
> The same code compiles perfectly for clang++ release
> (vector_copy_ellision_level=joinwithbinaryexpression) and for all
> configurations of g++.
>
> I don't think it is related to changes of current PR. I tried running it
> multiple times, but still the same error. Does anyone else has also faced
> the same issue before, or might know what is causing it?
>
> Building CXX object
>
types/operations/comparisons/CMakeFiles/quickstep_types_operations_comparisons_GreaterComparison.dir/GreaterComparison.cpp.o
> error: unable to execute command: Killed
> clang: error: clang frontend command failed due to signal (use -v to see
> invocation)
> Ubuntu clang version 3.7.1-svn253571-1~exp1 (branches/release_37) (based
> on LLVM 3.7.1)
> Target: x86_64-pc-linux-gnu
> Thread model: posix
> clang: note: diagnostic msg: PLEASE submit a bug report to
> http://bugs.debian.org/ and include the crash backtrace, preprocessed
> source, and associated run script.
> clang: note: diagnostic msg:
> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
> Preprocessed source(s) and associated run script(s) are located at:
> clang: note: diagnostic msg: /tmp/EqualComparison-835ea0.cpp
> clang: note: diagnostic msg: /tmp/EqualComparison-835ea0.sh
> clang: note: diagnostic msg:
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/incubator-quickstep/pull/101#issuecomment-251143502>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/ACZB64ofKH1SUORDDVv1CF96p_rYXoTWks5qwSPBgaJpZM4KCnYW>
> .
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
