similar to: [5.0.0 Release] Release Candidate 4 tagged

On Wed, Aug 30, 2017 at 2:14 PM, Michał Górny <mgorny at gentoo.org> wrote: > W dniu wto, 29.08.2017 o godzinie 16∶52 -0700, użytkownik Hans Wennborg > via llvm-dev napisał: >> Hello testers, >> >> 5.0.0-rc4 was just tagged. >> >> There were very few changes after rc3, and if nothing unexpected comes >> up, this is what the final release will look

Hello testers, 4.0.0-rc3 was just tagged from the branch at r296762. This is a release candidate in the real sense: if no major issues show up with this one, it is the version that will be released. Please let me know if you find any issues, including in release notes or documentation, which will be on the pre-release web site later today. Please build, test, and upload binaries to the sftp

Dear testers, 5.0.0-rc3 was just tagged. This is a release candidate in the real sense: if nothing bad comes up in testing, this is what the release is going to look like. Please build, test and upload binaries to the sftp (use the /data/testers-uploads/ directory) and let me know what issues remain. I know we're a little bit behind schedule, but hopefully we can get to 'final'

Dear testers, 6.0.0-rc3 was just tagged, after r325901 on the branch. There are still a few open blockers, but I'm not sure we'll actually end up blocking on all of them. So depending on what comes up, this release candidate is probably pretty close to what the final release will look like (I'm still hoping for more release notes, though). I'm hoping we can get to

Hello again, We had to pick up another bug fix, so here is another release candidate: llvmorg-11.0.0-rc5 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc5 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc5 Pre-built binaries will be added as they become ready. Please file reports for any bugs you find as blockers of

Dear testers, 5.0.0-rc2 was just tagged. I know we still have a bunch of open release blockers, but there has been a lot of merged patches and I'd like to find out what the status is. Please build, test and upload binaries to the sftp. When uploading, make sure to use the /data/testers-uploads/ directory on the server. Let me know if there are any issues. I'll upload sources, docs and

Hello everyone, A little less than a week after rc3, the llvmorg-11.0.0-rc4 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc4 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc4 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725

Hello testers, RC4 has just been tagged (at r229782 on the branch). RC3 was disqualified due to an infloop that Duncan reported, and fixed in r229421. That, fixes for a few scary X86 bugs, a GCC5 bootstrap problem (PR22625), and parts of PR22589 is included in RC4. Baring any showstoppers, this release candidate will be promoted to release. Please let me know how it looks and upload binaries

Dear testers, 8.0.0-rc5 was just tagged from the release_80 branch at r355909. This is identical to rc4 with the addition of r355743. Hopefully it is the final release candidate, so please give it a good testing. As usual, please run the test script, share your results, and upload binaries. I'll publish source tarballs and docs as soon as possible, and binaries as they become available.

Hello everyone, It took a bit longer than planned, but Release Candidate 3 is now here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at 3a843031a5 and contains 95 commits since the previous release candidate. If no new problems arise, this is what the final release will look like. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc3 and

On Tue, Aug 1, 2017 at 3:01 AM, Simon Dardis <Simon.Dardis at imgtec.com> wrote: > Currently I'm getting "Couldn't write to remote file "/home/testers/uploads/clang+llvm-5.0.0-rc1-mips-linux-gnu.tar.xz": Failure", > does that account need more space? Yes, the partition is full. I've asked Anton to see if we can fix this.

Dear testers, 3.7.0-rc4 has just been tagged. It is identical to rc3, plus: - r245902: Revert r245355: change of clang-tools-extra symlink in the release script - r245947: Merge of r245927: Fix LLDB build on MIPS - r245948: Deprecate the DataLayout on the TargetMachine, and backport the 3.8 API - Changes to the ReleaseNotes. Those changes should all be safe, and I expect this to be an extremely

Hi, I've tagged 6.0.1-rc3, which should be the last rc release. If every thing goes well, 6.0.1-final will be next Thursday. Testers please test 6.0.1-rc3 and upload the results. -Tom

I'm not aware of a bug filed for this, so please file one. I don't know much about the workings of test-suite myself, though. On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain <brian.cain at gmail.com> wrote: > Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem to be > failing for me with SIGILL. I'm guessing that my host CPU doesn't support

Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans

Final has been tagged, I think we're about to release it. On Fri, Feb 27, 2015 at 7:43 AM, Hayden Livingston <halivingston at gmail.com> wrote: > Are we waiting for an RC5? It seems like the release mirror on github has > no recent activity. > > On Wed, Feb 25, 2015 at 3:23 AM, Daniel Sanders <Daniel.Sanders at imgtec.com > > wrote: > >> Quick update

On 07/27/2017 05:17 PM, Tom Stellard via cfe-dev wrote: > On 07/26/2017 06:41 PM, Hans Wennborg via Release-testers wrote: >> Dear testers, >> >> 5.0.0-rc1 has just been tagged. >> > > Hi Hans, > > I see 1 regression one ppc64le: > > libomp :: tasking/omp_taskloop_grainsize.c > This isn't actually a regression, it's just a new test.

Hello testers, Start your engines, RC3 has just been tagged (at r229050 on the branch). If this one looks good, it will become the release. There has been quite a bit of activity on the branch since RC2; let's hope it's all goodness :-) Please let me know how it looks, and upload binaries to the sftp as usual. Thanks for all your efforts so far! - Hans

Quick update before I move on to the final tag. > clang+llvm-3.6.0-rc4-mipsel-linux-gnu.tar.xz > Still running due to a silly setup mistake on the first run (a broken > symlink to the test-suite source). Second attempt is a fair way through and > looks good so far though Default options were all good. Mips32 was about halfway but was good so far. >

SLES11 binaries for rc3 uploaded. 55b63de8adc12c67eb11abcf1a5f7132cca59b4e clang+llvm-6.0.0-rc3-x86_64-linux-sles11.3.tar.xz On Fri, Feb 23, 2018 at 9:14 AM, Hans Wennborg via Release-testers < release-testers at lists.llvm.org> wrote: > Dear testers, > > 6.0.0-rc3 was just tagged, after r325901 on the branch. > > There are still a few open blockers, but I'm not sure