Hi Tom, When running the test script, I got an error message: $ ./test-release.sh -no-64bit -release 3.4.2 -rc 1 -triple armv7a-linux-gnueabihf -j2 # Validating llvm SVN URL llvm 3.4.2 release candidate rc1 doesn't exist! Do I need to get another test-release.sh script? This is the one from release_34 branch we used to release 3.4.1. cheers, --renato On 16 May 2014 22:55, Tom Stellard <tom at stellard.net> wrote:> Hi, > > I have tagged 3.4.2 RC1 in SVN, so testers can begin testing. We > can always use more testers, so if you are interested in helping let me know. > > Test results from 3.4.2-rc1 should be checked for regressions against the 3.4.1 > release. When you submit results, please remind me the CPU and Operating System you are > testing with. > > Also, since 3.4.2 includes build fixes for gcc 4.9 it would be helpful if some people > could at least test building LLVM with gcc 4.9. I have already verified it works > on X86_64 Fedora, but more testing is welcomed. > > For the 3.4.1 release testers sent me uniformly named binary packages, which was very > nice. Is there a script you are using for generating these? > > Thanks again to all the volunteer testers. > > -Tom
I’m having the same issue. Thanks, -kevin On May 18, 2014, at 7:10 AM, Renato Golin <renato.golin at linaro.org> wrote:> Hi Tom, > > When running the test script, I got an error message: > > $ ./test-release.sh -no-64bit -release 3.4.2 -rc 1 -triple > armv7a-linux-gnueabihf -j2 > # Validating llvm SVN URL > llvm 3.4.2 release candidate rc1 doesn't exist! > > Do I need to get another test-release.sh script? This is the one from > release_34 branch we used to release 3.4.1. > > cheers, > --renato > > On 16 May 2014 22:55, Tom Stellard <tom at stellard.net> wrote: >> Hi, >> >> I have tagged 3.4.2 RC1 in SVN, so testers can begin testing. We >> can always use more testers, so if you are interested in helping let me know. >> >> Test results from 3.4.2-rc1 should be checked for regressions against the 3.4.1 >> release. When you submit results, please remind me the CPU and Operating System you are >> testing with. >> >> Also, since 3.4.2 includes build fixes for gcc 4.9 it would be helpful if some people >> could at least test building LLVM with gcc 4.9. I have already verified it works >> on X86_64 Fedora, but more testing is welcomed. >> >> For the 3.4.1 release testers sent me uniformly named binary packages, which was very >> nice. Is there a script you are using for generating these? >> >> Thanks again to all the volunteer testers. >> >> -Tom
On Sun, May 18, 2014 at 12:10:44PM +0100, Renato Golin wrote:> Hi Tom, > > When running the test script, I got an error message: > > $ ./test-release.sh -no-64bit -release 3.4.2 -rc 1 -triple armv7a-linux-gnueabihf -j2It should be: ./test-release.sh -no-64-bit -release 3.4 -dot 2 -rc 1 -triple armv7a-linux-gnueabihf -j2 -Tom> # Validating llvm SVN URL > llvm 3.4.2 release candidate rc1 doesn't exist! > > Do I need to get another test-release.sh script? This is the one from > release_34 branch we used to release 3.4.1. > > cheers, > --renato > > On 16 May 2014 22:55, Tom Stellard <tom at stellard.net> wrote: > > Hi, > > > > I have tagged 3.4.2 RC1 in SVN, so testers can begin testing. We > > can always use more testers, so if you are interested in helping let me know. > > > > Test results from 3.4.2-rc1 should be checked for regressions against the 3.4.1 > > release. When you submit results, please remind me the CPU and Operating System you are > > testing with. > > > > Also, since 3.4.2 includes build fixes for gcc 4.9 it would be helpful if some people > > could at least test building LLVM with gcc 4.9. I have already verified it works > > on X86_64 Fedora, but more testing is welcomed. > > > > For the 3.4.1 release testers sent me uniformly named binary packages, which was very > > nice. Is there a script you are using for generating these? > > > > Thanks again to all the volunteer testers. > > > > -Tom
Hi Renato, I used the 'test-release.sh' script from the tag. This is a bit awkward, as you have to do a first checkout by hand, and then use the script which will eventually do the another checkout :) Cheers, -- Arnaud On Mon, May 19, 2014 at 6:17 PM, Kevin Y. Kim <kykimnyc at gmail.com> wrote:> I’m having the same issue. > > Thanks, > -kevin > > On May 18, 2014, at 7:10 AM, Renato Golin <renato.golin at linaro.org> wrote: > > > Hi Tom, > > > > When running the test script, I got an error message: > > > > $ ./test-release.sh -no-64bit -release 3.4.2 -rc 1 -triple > > armv7a-linux-gnueabihf -j2 > > # Validating llvm SVN URL > > llvm 3.4.2 release candidate rc1 doesn't exist! > > > > Do I need to get another test-release.sh script? This is the one from > > release_34 branch we used to release 3.4.1. > > > > cheers, > > --renato > > > > On 16 May 2014 22:55, Tom Stellard <tom at stellard.net> wrote: > >> Hi, > >> > >> I have tagged 3.4.2 RC1 in SVN, so testers can begin testing. We > >> can always use more testers, so if you are interested in helping let me > know. > >> > >> Test results from 3.4.2-rc1 should be checked for regressions against > the 3.4.1 > >> release. When you submit results, please remind me the CPU and > Operating System you are > >> testing with. > >> > >> Also, since 3.4.2 includes build fixes for gcc 4.9 it would be helpful > if some people > >> could at least test building LLVM with gcc 4.9. I have already > verified it works > >> on X86_64 Fedora, but more testing is welcomed. > >> > >> For the 3.4.1 release testers sent me uniformly named binary packages, > which was very > >> nice. Is there a script you are using for generating these? > >> > >> Thanks again to all the volunteer testers. > >> > >> -Tom > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140519/a234f43a/attachment.html>
On 19 May 2014 20:11, Tom Stellard <tom at stellard.net> wrote:> ./test-release.sh -no-64-bit -release 3.4 -dot 2 -rc 1 -triple armv7a-linux-gnueabihf -j2*OF COURSE*! Silly me. Sorry about the noise. Do we have this in any doc already? --renato