similar to: [LLVMdev] 3.6.2-rc1 has been tagged. Testers needed.

On Wed, Jun 24, 2015 at 10:11:26AM -0700, Hans Wennborg wrote: > On Tue, Jun 23, 2015 at 5:17 PM, Tom Stellard <tom at stellard.net> wrote: > > I have just tagged 3.6.2-rc1, so testing can begin. We can always use > > more testers, so if you are interested in testing, let me know. > > I had trouble building on Windows, getting errors in > AMDGPUGenSubtargetInfo.inc

On 24 Jun 2015, at 22:29, Hans Wennborg <hans at chromium.org> wrote: > > On Wed, Jun 24, 2015 at 12:09 PM, Tom Stellard <tom at stellard.net> wrote: >> On Wed, Jun 24, 2015 at 10:11:26AM -0700, Hans Wennborg wrote: >>> On Tue, Jun 23, 2015 at 5:17 PM, Tom Stellard <tom at stellard.net> wrote: >>>> I have just tagged 3.6.2-rc1, so testing can

On Wed, Jul 01, 2015 at 09:38:15AM -0700, Dan Liew wrote: > Hi Tom, > > I'd like to backport some fixes in LLVM trunk to the 3.6 branch. These > changes only effect the generation of CMake files and should not > change the generated binaries. The changes are > > r240981 > r241080 > > which need to be applied in order. > > Is this okay? > No, it is

Hi, I have tagged 3.6.2-final, so testers can start building and uploading -final binaries. There was only one change between 3.6.2-rc1 and 3.6.2-final, which was a patch to the R600 backend to fix the build with VS2012. Running a full regression suite is probably not necessary, but you still can if you want to be extra careful. -Tom

Hi, I had a quick look at that link and it seems to be a linker internal error. Presumably we're triggering a bug in the system toolchain. FWIW, my mipsel build on a Debian Jessie machine (binutils 2.24.90.20141023-1) successfully completed test-release.sh. I'm currently running the tests. Here's the relevant bit of the log from your link: cd

> Test suite is green but I'm seeing two libc++ test failures when running check-all. What tests are failing? On Fri, Jun 10, 2016 at 5:13 PM, Nikola Smiljanic via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Uploaded Fedora and openSUSE binaries. Test suite is green but I'm seeing > two libc++ test failures when running check-all. I'm pretty sure these were >

clang+llvm-3.6.2-rc1-mipsel-linux-gnu.tar.xz The second test run finally finished (the machine lacks an FPU). All good. ________________________________________ From: Daniel Sanders Sent: 28 June 2015 18:51 To: Tom Stellard; llvmdev at cs.uiuc.edu Cc: cfe-dev at cs.uiuc.edu Subject: RE: 3.6.2-rc1 has been tagged. Testers needed. clang+llvm-3.6.2-rc1-mips-linux-gnu.tar.xz All good

I've uploaded clang+llvm-3.5.2-rc1-mips-linux-gnu.tar.xz and clang+llvm-3.5.2-rc1-mips-linux-gnu.tar.xz started testing them. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Daniel Sanders > Sent: 16 March 2015 15:36 > To: Tom Stellard; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Reminder 3.5.2

Hi, I have tagged the 3.6.1-rc1 so testing can begin. We can always use more testers, so if you are interested in helping, let me know. Instructions for validating an LLVM release can be found here: http://llvm.org/docs/ReleaseProcess.html Reminder: We are using 3.6.0 as our baseline for regression testing. Thanks, Tom

Hi, @CC'ing Hans because this will likely be of interest to you. Right I've started trying to build LLVM inside an Ubuntu chroot (Ubuntu 14.04LTS Docker image) and I've already come across a pretty bad bug in the ``test-release.sh`` script which potentially means that builds and/or tests could potentially fail without anyone noticing (unless someone carefully looks through the logs)

Hi, Just a reminder that testing for 3.5.2 will begin on Monday, Mar 16. If you have any patches you want merged please send an email to the relevant commits list and cc me and the code owner. If you have already done this and are waiting for a response, please ping the thread. As always we need testers, so let me know if you want to help with testing. Thanks, Tom

Hi, I'm not sure how important this will be but I found problems [1] with the way the test-release script creates packages. Specifically it's not using DESTDIR for the temporary tarball directory and instead is using --prefix and it really shouldn't be doing that. My observation so far has been that the only breakages I've seen are that the LLVM CMake export files have broken

Hi, I've tagged 3.8.1-rc1, testers can begin testing. -Tom

Hi, The only regression in 3.6.1 -rc1 was on MIPS and it has been confirmed fixed, so I have now tagged 3.6.1 -final. Testers can start building and uploading the final binaries. Thanks, Tom

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

On 28/03/2018 07:19, Tom Stellard via Release-testers wrote: > Hi, > > I've tagged 5.0.2-rc1, so testing can begin. LLVM_VERSION_PATCH is set to "1". Is that normal? (I was expecting "2"). http://llvm.org/viewvc/llvm-project/llvm/tags/RELEASE_502/rc1/CMakeLists.txt?revision=328512&view=markup#29 Thanks Sylvestre

Hi, I've created the 3.9.1-final tag no changes from -rc3. Testers can begin uploading binaries now. -Tom

Hi, I've tagged 3.8.1-final, so testers can start building the final binaries. -Tom

Daniel, Note the openmp library only has cmake build machinery preventing autoconf-based builds. Jack On Tue, Jun 23, 2015 at 10:18 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi, > > I'll do Mips as usual. Are we going to do an autoconf-based build for LLVM 3.7? If so, I might try Mips64 packages too. > >> -----Original

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