similar to: 5.0.2-rc1 tagged

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, We don't normally do X.Y.2 releases, but there has been some interest in getting a 5.0.2 release out with the Spectre mitigations included, so I am proposing the following schedule for a 5.0.2 release: LLVM 5.0.2 -rc1 Mon Mar 19 -final Mon Mar 26 To keep things easy for testers, 5.0.2 will be for Spectre related fixes only and won't be opened up for general bugs. And here is

Le 14/03/2018 à 00:29, Tom Stellard via Release-testers a écrit : > Hi, > > We don't normally do X.Y.2 releases, but there has been some interest in > getting a 5.0.2 release out with the Spectre mitigations included, so I > am proposing the following schedule for a 5.0.2 release: > > LLVM 5.0.2 > -rc1 Mon Mar 19 > -final Mon Mar 26 > > To keep things

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 >

Hi Tom, thanks and congrats for LLVM 10.0.1-rc1 release. [1] shows 2 assets. 10.0.0 RCs had a lot of more assets. I am missing the llvm-project-10.0.1rc1.tar.xz tarball. Will you provide them later or is there a new development/workflow decision I do not know of? BTW, the source zip and tar.gz tarballs show no sizes. I am using Mobile LTE/UMTS to download stuff from the Internet. For now I

Hi, I've fixed the version numbering and tagged 5.0.2-rc2. Testers can begin testing. -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 Wed, May 20, 2020 at 11:12 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/20/2020 09:53 AM, Sedat Dilek wrote: > > On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > >> > >> On 05/19/2020 09:05 PM, Sedat Dilek wrote: > >>> Hi Tom, > >>> > >>> thanks and congrats for LLVM

On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/19/2020 09:05 PM, Sedat Dilek wrote: > > Hi Tom, > > > > thanks and congrats for LLVM 10.0.1-rc1 release. > > > > [1] shows 2 assets. > > 10.0.0 RCs had a lot of more assets. > > I am missing the llvm-project-10.0.1rc1.tar.xz tarball. > > > > Will

Hi testers! 3.6.0-rc1 was just tagged, so testing can begin. I'm not super familiar with the testing script yet, but I believe the idea is to run it as follows: $ utils/release/test-release.sh -release 3.6.0 -rc 1 -triple x86_64-unknown-linux-gnu With the -triple value substituted for your platform. Bill's 3.5rc1 email also said 'test-suite' needs to be run by hand. Please

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

Hi, I just tagged LLVM 4.0.1-rc3, and it's ready for testing. If all goes well, we will do the final release on Monday. -Tom

On Wed, 13 Apr 2016 at 08:10 Amaury SECHET via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I'd like to shime in here. These apt repository used to contain packages > named llvm-3.8-tools containing, amongst other things, the lit python > library used to test llvm. It seems that it went away recently and I have > travis build failing because of this. > > What is

On Wed, 13 Apr 2016 at 09:38 Amaury SECHET <deadalnix at gmail.com> wrote: > I'd be happy to do it, but this is a bit much high level for me to be > actionable. Can you explain me what I should do to reintroduce them int he > debian packaging ? > On the CMake side, I'm not sure. I think it's just a matter of using the "install()" functions to install them

On 12/05/2014 16:13, Tom Stellard wrote: > On Mon, May 12, 2014 at 04:05:20PM +0200, Sylvestre Ledru wrote: >> On 12/05/2014 15:22, Tom Stellard wrote: >>> On Mon, May 12, 2014 at 08:41:36AM +0200, Sylvestre Ledru wrote: >>>> Hello, >>>> >>>> With the release of 3.4.1, the LLVM library has been renamed from >>>> libLLVM-3.4.so to

Hi, I've tagged the final version of 3.7.1. There is no difference from 3.7.1-rc2, so testers just need to build the packages no testing is required. -Tom

(cc'ing non-legacy llvm-dev this time; apologies if you get this twice. Please don't reply-all to the first one.) On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> wrote: > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There

On 12/05/2014 17:12, Tom Stellard wrote: > On Mon, May 12, 2014 at 04:17:05PM +0200, Sylvestre Ledru wrote: >> On 12/05/2014 16:13, Tom Stellard wrote: >>> On Mon, May 12, 2014 at 04:05:20PM +0200, Sylvestre Ledru wrote: >>>> On 12/05/2014 15:22, Tom Stellard wrote: >>>>> On Mon, May 12, 2014 at 08:41:36AM +0200, Sylvestre Ledru wrote:

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