similar to: [LLVMdev] [3.1 Release] Call For Testers!

On Mon, Apr 29, 2013 at 01:12:57PM -0700, Bill Wendling wrote: > Hear ye! Hear ye! This is a call for testers for the 3.3 release!!! > Is there an official timeline yet for the 3.3 release? > What's Expected > --------------- > > You might be asking yourself, "Self, I would like to be an LLVM tester for the 3.3 release, but I don't know what's involved in

On Mon, Apr 29, 2013 at 1:12 PM, Bill Wendling <wendling at apple.com> wrote: > Hear ye! Hear ye! This is a call for testers for the 3.3 release!!! > > What's Expected > --------------- > > You might be asking yourself, "Self, I would like to be an LLVM tester for > the 3.3 release, but I don't know what's involved in being one." Well, ask >

Not that I know of but it's definitely something we could use. The basic idea is to use the test-release.sh script that can be found in llvm source tree under utils/release. $ test-release.sh --help usage: test-release.sh -release X.Y -rc NUM [OPTIONS] -release X.Y The release number to test. -rc NUM The pre-release candidate number. -j NUM Number of compile jobs

Hear ye! Hear ye! This is a call for testers for the 3.3 release!!! What's Expected --------------- You might be asking yourself, "Self, I would like to be an LLVM tester for the 3.3 release, but I don't know what's involved in being one." Well, ask yourself no more! Not only do I have the answers for you, but talking to yourself will cause people to avoid you. Here's

Am Montag, den 02.06.2008, 23:52 -0700 schrieb Tanya Lattner: > All, > > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform. > > Directions to set up a tester are here: > http://llvm.org/docs/TestingGuide.html#nightly >

Hello, On Jun 3, 2008, at 08:52 , Tanya Lattner wrote: > All, > > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform. I think I might be able to set up a nightly tester for Linux x86 (32- bit). Although I've been following LLVM for

IMPORTANT! IMPORTANT! IMPORTANT! We will be branching for the 3.1 release on April 16th! :-) This gives us a little over two weeks to get the trees into the most stable condition we can. What this means for you: All major features for the 3.1 release should be finished or near completion by the April 16th. After April 16th, we will accept only bug fixes and patches which do not change the

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 have a project idea, that I may pursue in the future. In the meantime, I think I need to spend the next few months getting familiar with LLVM and the code, which I can do through svn (thank you). Also, for 2.5 and beyond, are you still in need of nightly testers? I will set up a Linux x86-64, and also have a Mac Pro (Leopard) for this. For Linux I plan on using the new Fedora 10,

> As always, we support Intel on Darwin, Debian and Ubuntu Linux, Windows, and > FreeBSD. We haven't released binaries for ARM, but that may change this time > around (no guarantees though). If you have a platform for which you would > like to see binaries released, let me know! My 2 cents: I think it would be great if dynamic libs were a part of the binary releases. That would

> I had planned to try again once 2.3 is out, but if you're short on Linux > testers, I'll join in. > > Available platforms: > * x86_64 > * i686 compatibility > Given that I had problems getting the latter to run, I think I should > concentrate on x86_64. > Should I switch PIC off for that? Thanks! Running a linux tester would be a huge help for the project.

To ensure that future releases of portable OpenSSH are as bug-free as possible, we need to recruit a team of testers. Each tester would be responsible for a particular OS platform and would be called upon to test snapshots before they are marked as official releases. The release would not go out until it had been given the OK by testers on each supported platform. A corollary of this is that

Hi, No major issues seen so far for mips. Binaries uploaded. SHA256(clang+llvm-6.0.0-rc3-mipsel-linux-gnu.tar.xz)= 6e4fab79cc341a9084dab94cced108daff39fcde14a11e8d7ae454e9f92cb77c SHA256(clang+llvm-6.0.0-rc3-mips-linux-gnu.tar.xz)= 54887a039d3d7ccff17a0c7245f4c9d778a1c22f96b619db554849da55293d61 SHA256(clang+llvm-6.0.0-rc3-x86_64-linux-gnu-debian8.tar.xz)=

Hi Hans, I'm seeing one unexpected failure: libc++ :: std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp Test logs show: Standard Error: -- terminating with uncaught exception of type std::length_error: basic_string -- but only on my big endian MIPS machine. I have filed PR36373 for the above failure. I've looked at the failures

We're now using it as the main compiler in the OpenMandriva development builds -- no issues so far (after rebuilding a couple of key packages for testing). ttyl bero On 17 January 2018 at 18:53, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > Dear testers, > > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open

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

On Mon, Dec 5, 2016 at 11:00 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 5 December 2016 at 18:56, Hans Wennborg via Release-testers > <release-testers at lists.llvm.org> wrote: >> The idea is that Tom's stable releases will keep incrementing the >> "patch" part of the version numbers, just as today, so they would be >> 4.0.1, 4.0.2,

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

All, We are in desperate need of linux x86 testers (32 or 64 bit). If you could set one up, the LLVM project would be very grateful. Right now we have virtually no testers covering this platform. Directions to set up a tester are here: http://llvm.org/docs/TestingGuide.html#nightly These directions could be improved of course. If you have any questions, I will be happy to assist you in

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