similar to: Xen 4.2.2-rc2 and 4.1.5-rc2 have been tagged

All, aiming at releases with once again not too many more RCs, please test! Thanks, Jan

On 03/29/2018 08:09 PM, Tom Stellard via Release-testers wrote: > Hi, > > I've fixed the version numbering and tagged 5.0.2-rc2. Testers can > begin testing. > So far, I've only received 5.0.2-rc2 binaries from 2 testers. I am guessing this is due to the mix up with -rc1 and the fact that we don't normally do X.Y.2 releases. If you would like to test this release

Xen 4.3.0-rc1 has been tagged, and a tarball is available from the wiki. Please note, there is one fairly major known bug in this release relating to the RTC clock. Windows 2003 is known not to install or boot at the moment. A fix has been checked in, but did not make it through testing in time to hit rc2; it should be included in rc3. In the mean time, if you find an operating system *other*

Hi, I've fixed the version numbering and tagged 5.0.2-rc2. Testers can begin testing. -Tom

On Wed, Nov 29, 2017 at 6:19 PM, Tom Stellard via Release-testers < release-testers at lists.llvm.org> wrote: > Hi, > > I've tagged the 5.0.1-rc2 release, go ahead and start testing and report > your results. > > > SLES11 uploaded. 1312db7bdfd05c82dd52983f8c5df1a6819df79f clang+llvm-5.0.1-rc2-linux-x86_64-sles11.3.tar.xz -------------- next part -------------- An

On Thu, Feb 05, 2015 at 04:28:55PM +0000, Renato Golin wrote: > On 31 January 2015 at 00:42, Hans Wennborg <hans at chromium.org> wrote: > > 3.6.0-rc2 was just tagged. Please test and build binaries. > > Hi Hans, > > I just built RC2 with the patch that fixes the NEON builds on ARM and > uploaded to the FTP site. It checks-all clean, but I'm running the >

Hi, Looks OK here. SHA256(clang+llvm-5.0.2-rc2-mipsel-linux-gnu.tar.xz)= 1c352e71a0d642eb5788ba259785076fa9df94928cf351d9fd6e643b077fb626 SHA256(clang+llvm-5.0.2-rc2-mips-linux-gnu.tar.xz)= 40369af514a55d8c75d05ec7ba141ce38872b10ba03dc606b1c88e3b5957f712 SHA256(clang+llvm-5.0.2-rc2-x86_64-linux-gnu-debian8.tar.xz)= e833e7a27919ad104c52b21abf5351c31e82dea51f8632f57a21c028b0cada97 Thanks, Simon

64bit Fedora Failing Tests (8): LeakSanitizer-AddressSanitizer :: TestCases/cleanup_in_tsd_destructor.cc LeakSanitizer-AddressSanitizer :: TestCases/disabler.cc LeakSanitizer-AddressSanitizer :: TestCases/disabler_in_tsd_destructor.cc LeakSanitizer-AddressSanitizer :: TestCases/ignore_object.cc LeakSanitizer-Standalone :: TestCases/cleanup_in_tsd_destructor.cc

Hi, There was one problem in -rc1, so we had to do another release candidate. -rc2 has now been tagged and is ready for testing. -Tom

On 31 Jan 2015, at 20:24, Hans Wennborg <hans at chromium.org> wrote: > > On Sat, Jan 31, 2015 at 9:24 AM, Dimitry Andric <dimitry at andric.com> wrote: ... >> This is because the ulimit -t 600 was exceeded, as shown in dmesg: >> >> pid 78288 (python2.7), uid 1000, was killed: exceeded maximum CPU limit >> >> Can we bump the -t limit a little?

Hi, I've tagged the 8.0.1-rc2 release, testers please begin testing and upload your binaries. There are still a few more bug fixes that I need to merge, so I'm planning to do one more release candidate before 8.0.1-final. -Tom

On Friday, July 31, 2015 07:50 AM, Hans Wennborg wrote: > Dear testers, > > 3.7.0-rc2 was just tagged. Please test, build binaries, upload to the > sftp, and report results to this thread. LNT is looking good on Ubuntu 14.04 x64, uploaded: clang+llvm-3.7.0-rc2-x86_64-linux-gnu-ubuntu-14.04.tar.xz The errors reported during build are: Failing Tests (17):

On Fri, Feb 8, 2019 at 9:53 AM Paweł Sikora via cfe-dev < cfe-dev at lists.llvm.org> wrote: > ----- Oryginalna wiadomość ----- > > Dear testers, > > > > 8.0.0-rc2 has been tagged from the release_80 branch at r353413. > > Hi, > > i've noticed a compile error with rc2 and libc++ (release_80 @svn). looks > similar to

> > Also, can you include Polly in the build as well? >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180824/43b39f77/attachment.html>

I'm just curious why you don't plan on using dlls? Xcode ships with libclang as a dylib, i wouldnt think windows would be a big leap? On Monday, August 27, 2018, Hans Wennborg <hans at chromium.org> wrote: > On Sat, Aug 25, 2018 at 12:03 AM, Marcus Johnson > <bumblebritches57 at gmail.com> wrote: > >> Don't forget to compile (everything if possible, but

> > Don't forget to compile (everything if possible, but especially LLVM) as a > shared library on Windows. > the installed toolchain is about 10 times bigger than the executable, because the static library is being compressed, which means on disk it's taking up far more space than it needs. > > > -------------- next part -------------- An HTML attachment was

Should I expect the "-openmp" to work for this RC? I got a link error (only in phase 3?). Maybe the fact that it happened in phase 3 suggests some hardware malfunction of mine? Or are there tests executed on phase 3 that aren't attempted on earlier phases? $ CC=clang CXX=clang++ ./test-release.sh -release 3.7.1 -rc 2 -j1 -openmp -triple armv7l-ubuntu15.10-linux-gnueabihf ... cd

On Sat, Jan 31, 2015 at 9:24 AM, Dimitry Andric <dimitry at andric.com> wrote: > 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. >>

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:

> > > clang+llvm-3.6.0-rc2-mipsel-linux-gnu.tar.xz > > > All clear for default options. > > > Still running for the other configs. > > > > I just had to kill Searching-dbl.simple and Packing-dbl.simple for the > > mips32 config which were at 65hrs and 15hrs real time respectively. This is > > far in excess of the 15,000s time limit that's