similar to: "R-testers" has gone the way of all mortals.. // History

The .Options vector had been introduced a while ago after my suggestion (see Ross's E-mail below). .Options$digits is used be default in several print methods (eg print.lm), however, deparse(.) e.g., uses options()$width, and not .Options$width. Another problem is that .Options is still not in the documentation (on-line help). Before one could add it there, we'd need ``the

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 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

Uploaded SLES11 and ubuntu 14.04. I can work on ubuntu 16.04 next. Is there any demand for ubuntu 17.10 releases? 4a0cb3e0ee573fb94e6c4f6be6c06eb661960471 clang+llvm-5.0.2-x86_64-linux-sles11.3.tar.xz 90430f7f0058100265352b1b2a2cd57e55558f92 clang+llvm-5.0.2-x86_64-linux-gnu-ubuntu-14.04.tar.xz On Thu, May 3, 2018 at 10:57 AM, Tom Stellard via Release-testers < release-testers at

On Sat, Dec 9, 2017 at 6:51 AM, Dimitry Andric via Release-testers < release-testers at lists.llvm.org> wrote: > On 8 Dec 2017, at 00:47, Tom Stellard via Release-testers < > release-testers at lists.llvm.org> wrote: > > I've just tagged 5.0.1-rc3, please test and report the results. > > Hopefully, this will be the last RC and the final release will > > be

When I tested rc1 I found that some of the test suite wouldn't build on SLES11.3 as a consequence of changes to the tests. At least some of the msan tests have been changed leverage features of glibc newer than is available on this platform. I asked about a minimum-required glibc but didn't hear back. Is the minimum required glibc for 3.9 different from 3.8? When I tried rc1 on

It's a test for the new interceptor for prlimit. It could be disabled with __GLIBC_PREREQ for 2.13+. On Fri, Aug 19, 2016 at 5:16 PM, Hans Wennborg <hans at chromium.org> wrote: > +Evgenii for msan. > > I suspect the community simply doesn't keep track of what glibc > version is required :-/ > > On Fri, Aug 19, 2016 at 5:10 PM, Brian Cain <brian.cain at

Ubuntu and SLES tarballs uploaded. I haven't had a chance to make a SLES12 build yet, but I will try in the coming days. f7553a0d66092ca0bbe1eab2af405523a18bafba clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-18.04.tar.xz 41db01a3b216df4fc22fae9c44e248889f9a01ed clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz caf149635742622a3a5b220146ff34f9202b8670

On 01/08/2019 11:36 AM, Ian Tessier via Release-testers wrote: > Can the ubuntu tarballs be published to the download site? They're not available yet. > These are up on the download site now. -Tom > On Mon, Dec 24, 2018 at 7:38 AM Brian Cain via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: > > Ubuntu and SLES tarballs

I must admit to being baffled by this. When I type "R" I get R : Copyright 1997, Robert Gentleman and Ross Ihaka Version 0.50 Beta (April 1, 1997) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type "license()" for details. > gc() Garbage collection ... 150427 cons cells free (75%) 1823k

> 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 >

rc1 did not exhibit this mismatch. A repeat of the rc2 build repeated the mismatch. I diff'd the disassembly between phase 2 and phase 3 and the difference is the same on both builds. The difference follows: # diff x86isel_p{2,3}.s 2c2 < Phase2/Release/llvmCore-8.0.0-rc2.obj/lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86ISelLowering.cpp.o: file format elf64-x86-64 --- >

On Wed, Nov 29, 2017 at 6:19 PM, Tom Stellard via Release-testers < release-testers at lists.llvm.org> wrote: > Hi, > > I've tagged the 5.0.1-rc2 release, go ahead and start testing and report > your results. > > > SLES11 uploaded. 1312db7bdfd05c82dd52983f8c5df1a6819df79f clang+llvm-5.0.1-rc2-linux-x86_64-sles11.3.tar.xz -------------- next part -------------- An

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

On 29 July 2016 at 23:57, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > There are still open merge requests and bugs, but I'd like to get the > real testing started to see where we're at. First wave of testing pass on ARM. Uploaded to the FTP server. Is it time to do the back-ports planned? I only have a very minor bug fix. cheers, --renato

Thanks! Can you post the sha1's for the files you uploaded? Windows and Mac look good. Uploaded: ca26fbfabb54ac1f70776ab3a5503313ec518f18 clang+llvm-3.9.0-rc2-x86_64-apple-darwin.tar.xz 26d616e1355dc0802f90babbd5ea0b72abc0c0bb LLVM-3.9.0-rc2-win32.exe 42363aeaff395d442f418d77b542a088b5b0658b LLVM-3.9.0-rc2-win64.exe Thanks, Hans On Fri, Aug 19, 2016 at 9:22 AM, Diana Picus <diana.picus

On Mon, Feb 29, 2016 at 2:20 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > clang+llvm-3.8.0-rc3-x86_64-linux-gnu-debian8.tar.xz (sha1sum: 2dedc6136d7cfbac8348652c543887964d92393c) > Native: All ok > Cross compiling to MIPS: All ok > > clang+llvm-3.8.0-rc3-mips-linux-gnu.tar.xz (sha1sum: f286149dbb2ea7e194c5c3719b6cded476f6e65f) > All ok

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 Wednesday, February 24, 2016 05:51 AM, Hans Wennborg via Release-testers wrote: > Dear testers, > > Release Candidate 3 has just been tagged [1]. Please build, test, and > upload to the sftp. Uploaded: clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-15.10.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz On

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