[llvm-dev] [10.0.0 Release] Release Candidate 1 is here (original) (raw)

Neil Nelson via llvm-dev llvm-dev at lists.llvm.org
Thu Feb 6 20:38:55 PST 2020

Uploaded for Xubuntu/Ubuntu 19.10.

sha256sum clang+llvm-10.0.0-rc1-x86_64-pc-linux-gnu.tar.xz 829c1f5a090666d2971b5f58fa34d24b5067a7969178bfc122a9b2df77432843

Is ParallelSTL something that should be installed? If so it is not clear at the ParallelSTL GitHub site and related pages how that should be done.

In logs directory. grep fail *.log | sort | uniq

deferred_errors.log:[Release+Asserts Phase3] check-all failed deferred_errors.log:[Release+Asserts Phase3] test suite failed deferred_errors.log:[Release Phase3] check-all failed deferred_errors.log:[Release Phase3] test suite failed llvm.check-Phase3-Release+Asserts.log:clang-10: clang-10: errorerror: : clang frontend command failed due to signal (use -v to see invocation)clang frontend command failed due to signal (use -v to see invocation) llvm.check-Phase3-Release+Asserts.log:clang-10: error: clang frontend command failed due to signal (use -v to see invocation) llvm.check-Phase3-Release+Asserts.log:clang-10: error: clang frontend command failed due to signal (use -v to see invocation) llvm.check-Phase3-Release+Asserts.log:: clang frontend command failed due to signal (use -v to see invocation) llvm.check-Phase3-Release+Asserts.log:clang frontend command failed due to signal (use -v to see invocation) llvm.check-Phase3-Release+Asserts.log:clang frontend command failed due to signal (use -v to see invocation)InstalledDir: /home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin llvm.check-Phase3-Release+Asserts.log:error#28:  clang frontend command failed due to signal (use -v to see invocation)0x000000000248cb2e llvm.check-Phase3-Release+Asserts.log::  error#7:  clang frontend command failed due to signal (use -v to see invocation)0x00007fa6cc086899 llvm.check-Phase3-Release.log:clang-10: error: clang frontend command failed due to signal (use -v to see invocation) llvm.configure-Phase1-Release+Asserts.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.configure-Phase1-Release.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.configure-Phase2-Release+Asserts.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.configure-Phase2-Release.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.configure-Phase3-Release+Asserts.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.configure-Phase3-Release.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.make-Phase1-Release+Asserts.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.make-Phase1-Release.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.make-Phase2-Release+Asserts.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.make-Phase2-Release.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.make-Phase3-Release+Asserts.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. llvm.make-Phase3-Release.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. testing.10.0.0-rc1.log:clang-10: clang-10: errorerror: : clang frontend command failed due to signal (use -v to see invocation)clang frontend command failed due to signal (use -v to see invocation) testing.10.0.0-rc1.log:clang-10: error: clang frontend command failed due to signal (use -v to see invocation) testing.10.0.0-rc1.log:clang-10: error: clang frontend command failed due to signal (use -v to see invocation) testing.10.0.0-rc1.log:: clang frontend command failed due to signal (use -v to see invocation) testing.10.0.0-rc1.log:clang frontend command failed due to signal (use -v to see invocation) testing.10.0.0-rc1.log:clang frontend command failed due to signal (use -v to see invocation)InstalledDir: /home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release/llvmCore-10.0.0-rc1.install/usr/local/bin testing.10.0.0-rc1.log:-- Could not find ParallelSTL, libc++abi will not attempt to use it but the build may fail if the libc++ in use needs it to be available. testing.10.0.0-rc1.log:error#28:  clang frontend command failed due to signal (use -v to see invocation)0x000000000248cb2e testing.10.0.0-rc1.log::  error#7:  clang frontend command failed due to signal (use -v to see invocation)0x00007fa6cc086899 testing.10.0.0-rc1.log:-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile testing.10.0.0-rc1.log:-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile testing.10.0.0-rc1.log:[Release+Asserts Phase3] check-all failed testing.10.0.0-rc1.log:[Release+Asserts Phase3] test suite failed testing.10.0.0-rc1.log:[Release Phase3] check-all failed testing.10.0.0-rc1.log:[Release Phase3] test suite failed

From testing.10.0.0-rc1.log testing.10.0.0-rc1.log:FAIL: LLVM :: tools/llvm-ar/quick-append.test (53138 of 69456) testing.10.0.0-rc1.log:******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test' FAILED ******************** testing.10.0.0-rc1.log:FAIL: LLVM :: tools/llvm-ar/quick-append.test (53160 of 69493) testing.10.0.0-rc1.log:******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test' FAILED ********************

SAME-NEXT: 1.o

             ^ :1:156: note: 'next' match was here /home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release+Asserts/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o ^ :1:105: note: previous match ended here /home/nnelson/Documents/llvm-project/llvm/utils/release/rc1/Phase3/Release+Asserts/llvmCore-10.0.0-rc1.obj/test/tools/llvm-ar/Output/quick-append.test.tmp/1.o ^

--

Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90..

15 warning(s) in tests

Testing Time: 696.88s

Failing Tests (1):     LLVM :: tools/llvm-ar/quick-append.test

  Expected Passes    : 67312   Expected Failures  : 272   Unsupported Tests  : 1908   Unexpected Failures: 1 make[3]: *** [CMakeFiles/check-all.dir/build.make:58: CMakeFiles/check-all] Error 1 make[3]: Target 'CMakeFiles/check-all.dir/build' not remade because of errors. make[2]: *** [CMakeFiles/Makefile2:358: CMakeFiles/check-all.dir/all] Error 2 make[1]: *** [CMakeFiles/Makefile2:365: CMakeFiles/check-all.dir/rule] Error 2 make[1]: Target 'check-all' not remade because of errors. make: *** [Makefile:238: check-all] Error 2 [Release+Asserts Phase3] check-all failed

Neil Nelson

On 1/30/20 12:38 PM, Hans Wennborg via llvm-dev wrote:

Hello everyone,

It took a bit longer than planned due to master being a somewhat unstable at the branch point, but Release Candidate 1 has now been tagged as llvmorg-10.0.0-rc1. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc1 Pre-built binaries will be added there as they become available. Please file bug reports for any issues you find as blockers of https://llvm.org/pr44555 Release testers: please start your engines, run the script, share your results, and upload binaries. Release Candidate 2 was previously scheduled for February 2. Because of the late RC1, I've pushed this back a bit to the 11th. Thanks, Hans

LLVM Developers mailing list llvm-dev at lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/b075eb66/attachment-0001.html>

More information about the llvm-dev mailing list