similar to: [6.0.0 Release] Release Candidate 1 tagged

Displaying 20 results from an estimated 20000 matches similar to: "[6.0.0 Release] Release Candidate 1 tagged"

2015 Jan 31
12
[LLVMdev] [3.6 Release] RC2 has been tagged, Testing Phase II begins
Hi testers, 3.6.0-rc2 was just tagged. Please test and build binaries. The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please file issues against it. Thanks for helping with the release! Hans
2020 Jan 30
21
[10.0.0 Release] Release Candidate 1 is here
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
2015 Jan 31
0
[LLVMdev] [3.6 Release] RC2 has been tagged, Testing Phase II begins
On 31 Jan 2015, at 01:42, Hans Wennborg <hans at chromium.org> wrote: > Hi testers, > > 3.6.0-rc2 was just tagged. Please test and build binaries. > > The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please > file issues against it. > > Thanks for helping with the release! This time I got an error during check-all, on i386-unknown-freebsd10:
2017 Feb 09
7
[4.0.0 Release] Release Candidate 2 has been tagged
Hello testers, 4.0.0-rc2 was just tagged from the branch at r294535. There are still open relase blocking bugs and merge requests, so this will not be the last release candidate, but we've had a lot of merges since the last one, and I'd like to see what the testing looks like. The test-release.sh script was updated to also include lld. Make sure you're using the latest version of
2020 Jun 27
9
10.0.1-rc2 release has been tagged
Hi, I've tagged the 10.0.1-rc2 release, please test the release and report any issues. Thanks, Tom
2018 Jan 19
3
[Release-testers] [6.0.0 Release] Release Candidate 1 tagged
On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >> >> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>> On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers >>> <release-testers at lists.llvm.org> wrote: >>>> Start
2017 Feb 09
2
[Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged
On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 4.0.0-rc2 was just tagged from the branch at r294535. > > Building on FreeBSD 10 at least didn't crash this time, and lld built just fine. :) I uploaded the following: >
2015 Mar 09
5
[LLVMdev] Build failure with compiler-rt on trunk under linux
I've been building clang on linux for a couple of years now, contributing to the testing on Ubuntu, but this one has me stumped: fatal error: 'asm/socket.h' file not found #include <asm/socket.h> [1556/4006] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.i386.dir/sanitizer_platform_limits_posix.cc.o FAILED:
2018 Jan 20
0
[Release-testers] [6.0.0 Release] Release Candidate 1 tagged
On 19 Jan 2018, at 17:11, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: >> On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >>> >>> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>>> On 17 Jan 2018, at 18:53, Hans Wennborg
2020 May 20
14
10.0.1-rc1 release has been tagged
Hi, I have just tagged the 10.0.1-rc1 release. Testers can begin testing and uploading binaries. If you still want to get a fix into the 10.0.1 release, you still have about a month to get your fix in. To request a patch be backported to the release/10.x branch, file a bug and mark it as a blocker of the release-10.0.1 meta bug. -Tom
2020 Feb 05
3
[Release-testers] [10.0.0 Release] Release Candidate 1 is here
Hello, When running test-release.sh using GCC 5.4.0 we encountered this error : /home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp: In function ‘llvm::StringLiteral clang::clangd::{anonymous}::getNameForExpr(const clang::Expr*)’: /home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp:450:10: error: could not convert
2018 Jun 07
2
[Release-testers] 6.0.1-rc2 has been tagged
On 06/05/2018 10:47 AM, Dimitry Andric wrote: > On 4 Jun 2018, at 18:01, Tom Stellard via Release-testers <release-testers at lists.llvm.org> wrote: >> >> The 6.0.1-rc2 release has been tagged. Testers may begin testing and >> reporting results. > > Built for FreeBSD 10, tested and uploaded: > > SHA256 (clang+llvm-6.0.1-rc2-amd64-unknown-freebsd10.tar.xz)
2018 Aug 03
10
[7.0.0 Release] rc1 has been tagged
Dear testers, 7.0.0-rc1 was just tagged (from the branch at r338847). It's early in the release process, but I'd like to find out what the status is of the branch on our various platforms. Please run the test script, share the results, and upload binaries. Thanks, Hans
2019 Feb 11
2
[Release-testers] [8.0.0 Release] rc2 has been tagged
rc1 did not exhibit this mismatch. A repeat of the rc2 build repeated the mismatch. I diff'd the disassembly between phase 2 and phase 3 and the difference is the same on both builds. The difference follows: # diff x86isel_p{2,3}.s 2c2 < Phase2/Release/llvmCore-8.0.0-rc2.obj/lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86ISelLowering.cpp.o: file format elf64-x86-64 --- >
2020 Jul 21
9
LLVM 10.0.1-final has been tagged
Hi, I've tagged 10.0.1-final. Testers, please begin uploading your binaries. Thanks, Tom
2014 Dec 12
9
[LLVMdev] 3.5.1 Testing Phase Begins
Hi, 3.5.1-rc1 has been tagged, so it is time to begin testing. We can always use more testers, so if you would like to volunteer, let me know. For those that are new to testing, please review the documentation for how validate a new release: http://llvm.org/docs/ReleaseProcess.html Remember that when we check for regressions we want to compare the test results of 3.5.1-rc1 with 3.5.0-final.
2018 Jan 18
2
[Release-testers] [6.0.0 Release] Release Candidate 1 tagged
Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: > On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers > <release-testers at lists.llvm.org> wrote: >> Start your engines; 6.0.0-rc1 was just tagged. >> >> I know there are still open blockers and it's early in the process in >> a way, but I'd like to find out where we are. Please run the
2019 Sep 13
2
[9.0.0 Release] Release Candidate 4 is here
It may be that the 'not' operator is not being found under bash at : 'RUN: at line 12';   not Perhaps this is would be better as the more commonly seen '!'. Neil Nelson On 9/13/19 12:12 PM, Neil Nelson via llvm-dev wrote: > > Toward the end of testing.9.0.0-rc4.log. > > Testing: 0 .. 10.. 20. > FAIL: Clang Tools :: clang-tidy/run-clang-tidy.cpp (17057 of
2018 Jan 18
0
[Release-testers] [6.0.0 Release] Release Candidate 1 tagged
On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open blockers and it's early in the process in > a way, but I'd like to find out where we are. Please run the test > script, let me know the results, and upload binaries. At the moment I
2020 Feb 06
3
[Release-testers] [10.0.0 Release] Release Candidate 1 is here
On Wed, Feb 5, 2020 at 9:30 PM Anil Mahmud <anil.mahmud.llvm at gmail.com> wrote: > > The following error was found when running test-release.sh on Red Hat 7.4 > > ******************** > FAIL: LLVM :: tools/llvm-ar/quick-append.test (53100 of 59657) > ******************** TEST 'LLVM :: tools/llvm-ar/quick-append.test' FAILED ******************** [...] >