similar to: [LLVMdev] [3.6 Release] RC1 has been tagged, Testing Phase I begins

Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] [3.6 Release] RC1 has been tagged, Testing Phase I begins"

2015 Jan 31
2
[LLVMdev] [3.6 Release] RC2 has been tagged, Testing Phase II begins
On Sat, Jan 31, 2015 at 9:24 AM, Dimitry Andric <dimitry at andric.com> wrote: > On 31 Jan 2015, at 01:42, Hans Wennborg <hans at chromium.org> wrote: >> Hi testers, >> >> 3.6.0-rc2 was just tagged. Please test and build binaries. >> >> The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please >> file issues against it. >>
2015 Jan 31
0
[LLVMdev] [3.6 Release] RC2 has been tagged, Testing Phase II begins
On 31 Jan 2015, at 01:42, Hans Wennborg <hans at chromium.org> wrote: > Hi testers, > > 3.6.0-rc2 was just tagged. Please test and build binaries. > > The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please > file issues against it. > > Thanks for helping with the release! This time I got an error during check-all, on i386-unknown-freebsd10:
2015 Jan 31
12
[LLVMdev] [3.6 Release] RC2 has been tagged, Testing Phase II begins
Hi testers, 3.6.0-rc2 was just tagged. Please test and build binaries. The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please file issues against it. Thanks for helping with the release! Hans
2015 Jan 31
1
[LLVMdev] [3.6 Release] RC2 has been tagged, Testing Phase II begins
On 31 Jan 2015, at 20:24, Hans Wennborg <hans at chromium.org> wrote: > > On Sat, Jan 31, 2015 at 9:24 AM, Dimitry Andric <dimitry at andric.com> wrote: ... >> This is because the ulimit -t 600 was exceeded, as shown in dmesg: >> >> pid 78288 (python2.7), uid 1000, was killed: exceeded maximum CPU limit >> >> Can we bump the -t limit a little?
2015 Jul 19
3
[LLVMdev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
On 19 Jul 2015, at 17:32, Dimitry Andric <dimitry at andric.com> wrote: > > On 19 Jul 2015, at 01:44, Dimitry Andric <dimitry at andric.com> wrote: > ... >> Hm, strangely enough, this version of the script does not go further than the Phase 2 installation, and does not run any tests? This used to work fine for the release_36 branch. >> >> I think it is
2015 Jan 19
6
[LLVMdev] [3.6 Release] RC1 has been tagged, Testing Phase I begins
On 15 January 2015 at 13:35, Renato Golin <renato.golin at linaro.org> wrote: > AArch64 tested and uploaded. ARMv7 in progress. Hi Hans, ARMv7 is giving me a bit of a headache... I've tried building on two different machines and I get the same error... Phase 2 completes successfully, but while building Phase 3, I get the error on *every* file: 1.
2015 May 11
8
[LLVMdev] 3.6.1 -rc1 has been tagged. Testing begins.
Hi, I have tagged the 3.6.1-rc1 so testing can begin. We can always use more testers, so if you are interested in helping, let me know. Instructions for validating an LLVM release can be found here: http://llvm.org/docs/ReleaseProcess.html Reminder: We are using 3.6.0 as our baseline for regression testing. Thanks, Tom
2017 Jul 31
0
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
On 31 Jul 2017, at 19:26, Hans Wennborg <hans at chromium.org> wrote: > > On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric <dimitry at andric.com> wrote: >> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote: >>> >>> 5.0.0-rc1 has just been tagged. >>> >>> Please build, test and upload binaries
2018 Feb 08
0
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > > 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. Built, tested and uploaded: SHA256
2015 Aug 28
2
[3.7 Release] 3.7.0-final has been tagged
On 28 Aug 2015, at 20:12, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Aug 27, 2015 at 6:46 PM, Hans Wennborg <hans at chromium.org> wrote: >> I have promoted RC4 to final; 3.7.0 has reached its final state. >> >> Thanks for all your hard work so far. Please build and upload binaries >> with "-final", and let's ship this next
2018 Jan 20
0
[Release-testers] [6.0.0 Release] Release Candidate 1 tagged
On 19 Jan 2018, at 17:11, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: >> On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >>> >>> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>>> On 17 Jan 2018, at 18:53, Hans Wennborg
2018 Jan 19
3
[Release-testers] [6.0.0 Release] Release Candidate 1 tagged
On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >> >> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>> On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers >>> <release-testers at lists.llvm.org> wrote: >>>> Start
2017 Dec 07
7
5.0.1-rc3 has been tagged
Hi, 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 next week. -Tom
2015 Feb 18
13
[LLVMdev] [3.6 Release] RC4 has been tagged
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
2015 May 20
9
[LLVMdev] 3.6.1 -final has been tagged
Hi, The only regression in 3.6.1 -rc1 was on MIPS and it has been confirmed fixed, so I have now tagged 3.6.1 -final. Testers can start building and uploading the final binaries. Thanks, Tom
2018 Jun 07
2
[Release-testers] 6.0.1-rc2 has been tagged
On 06/05/2018 10:47 AM, Dimitry Andric wrote: > On 4 Jun 2018, at 18:01, Tom Stellard via Release-testers <release-testers at lists.llvm.org> wrote: >> >> The 6.0.1-rc2 release has been tagged. Testers may begin testing and >> reporting results. > > Built for FreeBSD 10, tested and uploaded: > > SHA256 (clang+llvm-6.0.1-rc2-amd64-unknown-freebsd10.tar.xz)
2017 Jul 31
3
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric <dimitry at andric.com> wrote: > On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote: >> >> 5.0.0-rc1 has just been tagged. >> >> Please build, test and upload binaries to the sftp. Let me know if >> there are any issues. > > Built and tested rc1. Test failures on
2018 Feb 07
12
[6.0.0 Release] Release Candidate 2 tagged
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
2017 Jun 14
5
LLVM 4.0.1 -rc3 has been tagged
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
2015 Jun 25
2
[LLVMdev] [cfe-dev] 3.6.2-rc1 has been tagged. Testers needed.
On 24 Jun 2015, at 22:29, Hans Wennborg <hans at chromium.org> wrote: > > On Wed, Jun 24, 2015 at 12:09 PM, Tom Stellard <tom at stellard.net> wrote: >> On Wed, Jun 24, 2015 at 10:11:26AM -0700, Hans Wennborg wrote: >>> On Tue, Jun 23, 2015 at 5:17 PM, Tom Stellard <tom at stellard.net> wrote: >>>> I have just tagged 3.6.2-rc1, so testing can