Re: [lldb-dev] [3.8 Release] Schedule and call for testers

On 12 Dec 2015, at 00:14, Hans Wennborg wrote: > > It's not quite time to start the 3.8 release process, but it's time to > start planning. > > Please let me know if you want to help with testing and building > release binaries for your favourite platform. (If you were a tester on > the previous

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

Unfortunately I'm having lots of trouble with rc1 at this point: * libcxxabi can't build, because it requires unwind.h, which we do not yet have on FreeBSD 10.x (Ed Maste is working on it for 11.x, but that is not ready for general consumption). * The test-release.sh script has no option to disab

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

On 20 Jan 2016, at 18:23, Hans Wennborg wrote: > > On Wed, Jan 20, 2016 at 5:25 AM, Dimitry Andric wrote: >> Unfortunately I'm having lots of trouble with rc1 at this point: >> * libcxxabi can't build, because it requires unwind.h, which we do not yet >> have on FreeBSD 10.x (Ed Maste is workin

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

On 20 Jan 2016, at 22:26, Hans Wennborg wrote: > > On Wed, Jan 20, 2016 at 12:18 PM, Dimitry Andric wrote: ... >> The way I fixed this during the 3.7 test phase, is by changing >> test-release.sh so it exports directly into these locations: >> >> # Exporting llvm 3.7.0-rc3 sources to llvm.src

Re: [lldb-dev] [llvm-dev] [3.8 Release] RC1 has been tagged

On 20 Jan 2016, at 21:18, Dimitry Andric via llvm-dev wrote: ... >>> * Last but not least: the host compiler on FreeBSD 10.x is clang 3.4.1 (the >>> last version that can build without C++11 support), and it crashes with a >>> segfault during building of CGBlocks.cpp. I'll need to find some wa

Re: [lldb-dev] [Release-testers] [3.8 Release] RC2 has been tagged

On 02 Feb 2016, at 22:15, Hans Wennborg via Release-testers wrote: > > Release Candidate 2 has just been tagged [1]. Please build, test, and > upload to the sftp. > > I know there are still outstanding issues from RC1, but there have > been a lot of merges going into the branch and I think it's

Re: [lldb-dev] [Release-testers] [3.8 Release] RC2 has been tagged

On 04 Feb 2016, at 09:09, Dimitry Andric via Release-testers wrote: > > On 02 Feb 2016, at 22:15, Hans Wennborg via Release-testers > wrote: >> >> Release Candidate 2 has just been tagged [1]. Please build, test, and >> upload to the sftp. >> >> I know there are still outstanding issues from

Re: [lldb-dev] [Release-testers] [3.8 Release] RC3 has been tagged

On 23 Feb 2016, at 22:51, Hans Wennborg via Release-testers wrote: > > Release Candidate 3 has just been tagged [1]. Please build, test, and > upload to the sftp. Built and tested just fine on FreeBSD 10. Uploaded the following tarballs: SHA256 (clang+llvm-3.8.0-rc3-amd64-unknown-freebsd10.ta

Re: [lldb-dev] [Release-testers] [3.8 Release] 'final' has been tagged

On 03 Mar 2016, at 01:33, Hans Wennborg via Release-testers wrote: > > My list of blockers is empty, and there were no new problems > discovered with rc3, so I have gone ahead and tagged 3.8.0-final [1]. > > Please build the final binaries and upload to the sftp. Built and tested successfully

Re: [lldb-dev] [cfe-dev] [3.9 Release] Release plan and call for testers

On 10 Jun 2016, at 22:38, Hans Wennborg via cfe-dev wrote: > It's time to start planning for the 3.9 release. > > Please let me know if you'd like to help providing binaries and > testing for your favourite platform. As usual, I volunteer for providing FreeBSD binaries and testing. > I propo

Re: [lldb-dev] [Release-testers] [3.9 Release] Release Candidate 1 has been tagged

On 30 Jul 2016, at 00:57, Hans Wennborg via Release-testers wrote: > > 3.9.0-rc1 was just tagged from the 3.9 branch at r277207. After fixing two compiler-rt test failures (see r277297 and r277300) and one openmp test link failure (see https://reviews.llvm.org/D23084), I'm left with only two

Re: [lldb-dev] [cfe-dev] [Release-testers] [3.9 Release] Release Candidate 1 has been tagged

On 03 Aug 2016, at 20:44, Renato Golin wrote: > > On 3 August 2016 at 19:24, Dimitry Andric via cfe-dev > wrote: >> Unfortunately this is in TSan, which does not work at all on FreeBSD 11 and >> higher, due to a conflict of initialization order with our jemalloc. So I >> am not extremely keen

Re: [lldb-dev] [Release-testers] [3.9 Release] Release Candidate 2 has been tagged

On 19 Aug 2016, at 03:51, Hans Wennborg via Release-testers wrote: > > 3.9.0-rc2 was just tagged from the 3.9 branch at r279183. > > This is a release candidate in the very real sense that if nothing new > comes up, this is be what the final release looks like. There are > currently no open rel

Re: [lldb-dev] [Release-testers] [3.9 Release] Release Candidate 3 has been tagged

On 25 Aug 2016, at 05:42, Hans Wennborg via Release-testers wrote: > > 3.9.0-rc3 was just tagged from the branch at r279704. > > This one is very similar to rc2. These are the only new commits: > > r279224 - Minor change to OpenCL release notes > r279260 - [lld] Add a note that 3.9 is a major

Re: [lldb-dev] [Release-testers] [3.9 Release] 'final' has been tagged

On 01 Sep 2016, at 01:49, Hans Wennborg via Release-testers wrote: > > The final version of 3.9.0 was just tagged (from the 3.9 branch at > r280312). There were no changes after rc3. This took a little longer > than expected, but on the up side that means it's had more time to be > tested. Buil

Re: [lldb-dev] [Openmp-dev] [4.0 Release] Schedule and call for testers

On 05 Dec 2016, at 19:26, Hans Wennborg via Openmp-dev wrote: > > There's still plenty of time left, but I'd like to get the schedule > set before folks start disappearing for the holidays. > > Note that this release will also switch us to the new versioning > scheme where the major version is

Re: [lldb-dev] [Release-testers] [4.0.0 Release] Relase Candidate 1 has been tagged

On 18 Jan 2017, at 16:45, Hans Wennborg via Release-testers wrote: > Dear testers, > > 4.0.0-rc1 was just tagged from the branch, with r292377. > > There are still open merge requests and bugs, but I'd like to get the > testing started to see what issues come up. Unfortunately no builds for Fr

Re: [lldb-dev] [Release-testers] [4.0.0 Release] Relase Candidate 1 has been tagged

On 19 Jan 2017, at 16:40, Hans Wennborg wrote: > > On Thu, Jan 19, 2017 at 12:12 AM, Dimitry Andric wrote: >> On 18 Jan 2017, at 16:45, Hans Wennborg via Release-testers >> wrote: >>> Dear testers, >>> >>> 4.0.0-rc1 was just tagged from the branch, with r292377. >>> >>> There are still open

Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers wrote: > > 4.0.0-rc2 was just tagged from the branch at r294535. Building on FreeBSD 10 at least didn't crash this time, and lld built just fine. :) I uploaded the following: SHA256 (clang+llvm-4.0.0-rc2-i386-unknown-freebsd10.tar.xz

Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 3 has been tagged

On 2 Mar 2017, at 20:47, Hans Wennborg via Release-testers wrote: > 4.0.0-rc3 was just tagged from the branch at r296762. > > This is a release candidate in the real sense: if no major issues show > up with this one, it is the version that will be released. > > Please let me know if you find an

Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 3 has been tagged

On 3 Mar 2017, at 21:09, Dimitry Andric via Release-testers wrote: > > On 2 Mar 2017, at 20:47, Hans Wennborg via Release-testers > wrote: >> 4.0.0-rc3 was just tagged from the branch at r296762. >> >> This is a release candidate in the real sense: if no major issues show >> up with this one,

Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 4 has been tagged

> On 7 Mar 2017, at 22:15, Hans Wennborg via Release-testers > wrote: > > Dear testers, > > 4.0.0-rc4 was just tagged from the branch at r297204. > > This is very similar to rc3, with additional fixes for PR32142 and PR32153. > > Please take it for a quick spin. If nothing new comes up, this

Re: [lldb-dev] [Release-testers] [4.0.0 Release] 'final' has been tagged

On 9 Mar 2017, at 01:52, Hans Wennborg via Release-testers wrote: > The final version of 4.0.0 was just tagged (from the 4.0 branch at > r297335). There were no changes after rc4. > > Please build the final binaries and upload to the sftp. Built and tested OK on FreeBSD 10. I have uploaded: S

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev 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 amd64-freebsd10: FAIL: LLVM-Unit :: ExecutionEngine/Orc/./OrcJI

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On 31 Jul 2017, at 19:26, Hans Wennborg wrote: > > On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric wrote: >> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev >> wrote: >>> >>> 5.0.0-rc1 has just been tagged. >>> >>> Please build, test and upload binaries to the sftp. Let me know if >>> th

Re: [lldb-dev] [Release-testers] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On 31 Jul 2017, at 20:13, Dimitry Andric via Release-testers wrote: > > On 31 Jul 2017, at 19:26, Hans Wennborg wrote: >> >> On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric wrote: >>> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev >>> wrote: 5.0.0-rc1 has just been tagged. >

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

On 11 Aug 2017, at 04:00, Hans Wennborg via Release-testers wrote: > 5.0.0-rc2 was just tagged. > > I know we still have a bunch of open release blockers, but there has > been a lot of merged patches and I'd like to find out what the status > is. As in the last rc, most of the ASan tests failed

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

On 24 Aug 2017, at 23:48, Hans Wennborg wrote: > > On Mon, Aug 14, 2017 at 3:36 AM, Dimitry Andric wrote: >> On 11 Aug 2017, at 04:00, Hans Wennborg via Release-testers >> wrote: >>> 5.0.0-rc2 was just tagged. >>> >>> I know we still have a bunch of open release blockers, but there has >>> be

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 3 tagged

On 26 Aug 2017, at 00:52, Hans Wennborg via Release-testers wrote: > > 5.0.0-rc3 was just tagged. > > This is a release candidate in the real sense: if nothing bad comes up > in testing, this is what the release is going to look like. Built and tested, no changes with respect to the previous r

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 4 tagged

On 30 Aug 2017, at 01:52, Hans Wennborg via Release-testers wrote: > > 5.0.0-rc4 was just tagged. > > There were very few changes after rc3, and if nothing unexpected comes > up, this is what the final release will look like. Built and tested on FreeBSD 10, no changes with respect to the previ

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 5 tagged

On 1 Sep 2017, at 23:07, Hans Wennborg via Release-testers wrote: > > 5.0.0-rc5 was just tagged. > > I had hoped rc4 would be the last one, but I think we needed the fix > for PR34381. Built and tested on FreeBSD 10, no changes with respect to the previous rc. I've uploaded: SHA256 (clang+l

Re: [lldb-dev] [Release-testers] [5.0.0 Release] The final tag is in

On 5 Sep 2017, at 20:24, Hans Wennborg via Release-testers wrote: > > The final version of 5.0.0 has just been tagged. There were no changes > after rc5. Built and tested on FreeBSD 10, and uploaded: SHA256 (clang+llvm-5.0.0-amd64-unknown-freebsd10.tar.xz) = e55b646390da0a24e27f9761eecf0b3193

Re: [lldb-dev] [cfe-dev] [6.0.0 Release] Scheduling the release

On 6 Dec 2017, at 18:28, Hans Wennborg via cfe-dev wrote: > > It's time to start making plans for the 6.0.0 release. > > Following our regular schedule, the branch would occur about two weeks > into January, on Wednesday 17 January 2018, with the goal of shipping > early March. This is the sche

Re: [lldb-dev] [cfe-dev] [6.0.0 Release] Release Candidate 1 tagged

On 17 Jan 2018, at 18:53, Hans Wennborg via cfe-dev wrote: > > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open blockers and it's early in the process in > a way, but I'd like to find out where we are. For an overview of what failed in the FreeBSD ports collection

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers wrote: > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open blockers and it's early in the process in > a way, but I'd like to find out where we are. Please run the test > script, let me know the results, and

Re: [lldb-dev] [llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

On 18 Jan 2018, at 15:03, Jonas Hahnfeld 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 >> wrote: >>> Start your engines; 6.0.0-rc1 was just tagged. >>> I know there are still open blockers and it's early in the

Re: [lldb-dev] Apple LLDB 900.0.64 crash

Hi Johan, If it is Apple specific, create a report on the Apple Bug Reporter, at https://bugreport.apple.com/ . If you can reproduce the error with stock lldb, please report it on the LLVM bugtracker, at https://bugs.llvm.org/enter_bug.cgi

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers wrote: > > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open blockers and it's early in the process in > a way, but I'd like to find out where we are. Please run the test > script, let me know the results,

Re: [lldb-dev] [llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

On 19 Jan 2018, at 17:11, Hans Wennborg wrote: > > On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric wrote: >> On 18 Jan 2018, at 15:03, Jonas Hahnfeld 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

Re: [lldb-dev] [Release-testers] [llvm-dev] [6.0.0 Release] Release Candidate 1 tagged

On 20 Jan 2018, at 13:32, Dimitry Andric via Release-testers wrote: > > On 19 Jan 2018, at 17:11, Hans Wennborg wrote: >> >> On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric wrote: >>> On 18 Jan 2018, at 15:03, Jonas Hahnfeld wrote: Am 2018-01-18 14:55, schrieb Dimitry Andric via l

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers 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 upl

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

> On 9 Feb 2018, at 10:20, Hans Wennborg wrote: > > On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric wrote: >> On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers >> wrote: >>> >>> There's been a lot of merges since rc1, and hopefully the tests are in >>> a better state now. >>> >>> 6

Re: [lldb-dev] [cfe-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev wrote: > >> On 9 Feb 2018, at 10:20, Hans Wennborg wrote: ... >> What are all these test failures? Does it seems like they have a >> common root cause and do we have a bug for it? ... > The Clang Tools and Extra Tools Unit tests all appear to

Re: [lldb-dev] [Openmp-dev] [cfe-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev wrote: > > On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev > wrote: >> >>> On 9 Feb 2018, at 10:20, Hans Wennborg wrote: > ... >>> What are all these test failures? Does it seems like they have a >>> common root cause and do we have

Re: [lldb-dev] [Openmp-dev] [cfe-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

On 9 Feb 2018, at 22:30, Dimitry Andric wrote: > > On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev > wrote: >> >> On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev >> wrote: >>> On 9 Feb 2018, at 10:20, Hans Wennborg wrote: >> ... What are all these test failures? Does i

Re: [lldb-dev] [Openmp-dev] [6.0.0 Release] Release Candidate 3 tagged

On 23 Feb 2018, at 16:14, Hans Wennborg via Openmp-dev wrote: > 6.0.0-rc3 was just tagged, after r325901 on the branch. > > There are still a few open blockers, but I'm not sure we'll actually > end up blocking on all of them. So depending on what comes up, this > release candidate is probably p

Re: [lldb-dev] [Release-testers] [6.0.0 Release] The final tag is in

On 2 Mar 2018, at 13:17, Hans Wennborg via Release-testers wrote: > > The final version of 6.0.0 has just been tagged from the branch after > r326550. It has the same contents as -rc3 modulo release notes and one > small x86 fix (r326393). > > Please build the final binaries and upload to the s

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers wrote: > > 7.0.0-rc1 was just tagged (from the branch at r338847). > > It's early in the release process, but I'd like to find out what the > status is of the branch on our various platforms. > > Please run the test script, share the r

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 6 Aug 2018, at 18:23, Hans Wennborg wrote: > > On Sun, Aug 5, 2018 at 5:49 PM, Dimitry Andric wrote: >> On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers >> wrote: >>> >>> 7.0.0-rc1 was just tagged (from the branch at r338847). ... > >> Hmm, I'm running into a rather nasty snag n

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers wrote: > > Dear testers, > > 7.0.0-rc1 was just tagged (from the branch at r338847). > > It's early in the release process, but I'd like to find out what the > status is of the branch on our various platforms. > > Please run the test

Re: [lldb-dev] [llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 16 Aug 2018, at 00:51, Joerg Sonnenberger via llvm-dev wrote: > > On Tue, Aug 07, 2018 at 09:49:16PM +0200, Dimitry Andric via llvm-dev wrote: >> This is a regression caused by https://reviews.llvm.org/rL323281: >> >> >

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 16 Aug 2018, at 00:51, Joerg Sonnenberger via llvm-dev wrote: > On Tue, Aug 07, 2018 at 09:49:16PM +0200, Dimitry Andric via llvm-dev wrote: >> This is a regression caused by https://reviews.llvm.org/rL323281: >> >> >> r

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 22 Aug 2018, at 05:58, Wei Mi wrote: > > On Fri, Aug 17, 2018 at 1:27 PM, Dimitry Andric wrote: > On 16 Aug 2018, at 00:51, Joerg Sonnenberger via llvm-dev > wrote: > > On Tue, Aug 07, 2018 at 09:49:16PM +0200, Dimitry Andric via llvm-dev wrote: > >> This is a regression caused by https://r

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 22 Aug 2018, at 18:45, Hans Wennborg wrote: > > On Wed, Aug 22, 2018 at 3:48 AM, Dimitry Andric wrote: >> On 22 Aug 2018, at 05:58, Wei Mi wrote: >>> >>> On Fri, Aug 17, 2018 at 1:27 PM, Dimitry Andric wrote: >>> On 16 Aug 2018, at 00:51, Joerg Sonnenberger via llvm-dev >>> wrote: O

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc2 has been tagged

On 23 Aug 2018, at 01:59, Hans Wennborg via Release-testers wrote: > > 7.0.0-rc2 was just tagged (from branch revision r340437). > > There have been a bunch of merges since rc1, and hopefully many of the > issues with the previous candidate are fixed in this one. By reverting r323281 locally,

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 25 Aug 2018, at 00:51, Hans Wennborg wrote: > > On Wed, Aug 22, 2018 at 10:33 PM, Dimitry Andric wrote: >> On 22 Aug 2018, at 18:45, Hans Wennborg wrote: >>> >>> On Wed, Aug 22, 2018 at 3:48 AM, Dimitry Andric wrote: On 22 Aug 2018, at 05:58, Wei Mi wrote: ... > Sorry I missed th

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc2 has been tagged

On 27 Aug 2018, at 10:29, Hans Wennborg wrote: > > On Sat, Aug 25, 2018 at 12:46 PM, Dimitry Andric wrote: ... >> Unfortunately the test-suite doesn't build on i386, since quite a few of its >> components requires SSE2, and the build shows many errors like: >> >> /home/dim/llvm/7.0.0/rc2/test-

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc3 has been tagged

On 10 Sep 2018, at 16:12, Hans Wennborg via Release-testers wrote: > 7.0.0-rc3 was just tagged (from branch revision r341805). > > No further release candidates are currently planned, so this is a > release candidate in the real sense: unless any serious issues > surface, this is what the final

Re: [lldb-dev] [Release-testers] [7.0.0 Release] The final tag is in

On 17 Sep 2018, at 13:41, Hans Wennborg via Release-testers wrote: > > The final version of 7.0.0 has been tagged from the branch at r342370. > It is identical to rc3 modulo release notes and docs changes. There weren't any code changes relative to rc3, so nothing changed in the test results e

Re: [lldb-dev] [llvm-dev] 7.0.1-rc2 release has been tagged please begin testing

On 3 Nov 2018, at 03:35, Tom Stellard via llvm-dev wrote: > > The 7.0.1-rc2 release has been tagged and is ready for testing. I forgot > to bump the version number to 7.0.1 before I tagged -rc1, which is why we > are now on -rc2. Main test results on amd64-freebsd11 are mostly unchanged from 7

Re: [lldb-dev] [Release-testers] LLVM 7.0.1-rc3 has been tagged.

On 8 Dec 2018, at 06:29, Tom Stellard via Release-testers wrote: > > I've just tagged 7.0.1-rc3. This will hopefully be the last release > candidate. > Please test and report results. Main test results on amd64-freebsd11 have 12 more Expected Passes compared to 7.0.1 rc2, and 2 more Unexpect

Re: [lldb-dev] [Release-testers] 7.0.1-final has been tagged

On 20 Dec 2018, at 01:23, Tom Stellard via Release-testers wrote: > > I've tagged the 7.0.1 final release. Testers may begin uploading binaries. Main test results on amd64-freebsd11 had 1 more Expected Pass compared to 7.0.1 rc3, and no more Passes With Retry: Expected Passes: 52445(

Re: [lldb-dev] [Release-testers] [8.0.0 Release] rc1 has been tagged

On 24 Jan 2019, at 01:49, Hans Wennborg via Release-testers wrote: > > 8.0.0-rc1 was just tagged (from the branch at r351980). > > It took a little longer than planned, but it's looking good. > > Please run the test script, share your results, and upload binaries. Unfortunately I'm running in

Re: [lldb-dev] [Release-testers] [8.0.0 Release] rc1 has been tagged

On 24 Jan 2019, at 20:34, Michał Górny wrote: > > On Thu, 2019-01-24 at 19:58 +0100, Dimitry Andric via Release-testers > wrote: >> On 24 Jan 2019, at 01:49, Hans Wennborg via Release-testers >> wrote: >>> >>> 8.0.0-rc1 was just tagged (from the branch at r351980). >>> >>> It took a little lo

Re: [lldb-dev] [Release-testers] [8.0.0 Release] rc1 has been tagged

On 24 Jan 2019, at 21:25, Dimitry Andric via Release-testers wrote: > > On 24 Jan 2019, at 20:34, Michał Górny wrote: >> >> On Thu, 2019-01-24 at 19:58 +0100, Dimitry Andric via Release-testers wrote: >>> On 24 Jan 2019, at 01:49, Hans Wennborg via Release-testers >>> wrote: 8.0.0

Re: [lldb-dev] [Release-testers] [8.0.0 Release] rc2 has been tagged

On 7 Feb 2019, at 16:41, Hans Wennborg via Release-testers wrote: > 8.0.0-rc2 has been tagged from the release_80 branch at r353413. > > Please run the test script, share your results, and upload binaries. Unfortunately I had to disable compiler-rt for this test run, as most of the sanitizers

Re: [lldb-dev] [Release-testers] [8.0.0 Release] rc3 has been tagged

On 27 Feb 2019, at 19:51, Hans Wennborg via Release-testers wrote: > > 8.0.0-rc3 was just tagged from the release_80 branch at r355015. > > We're running a little behind schedule now, but I think we're also > close to be able to call this done. Again, I had to disable compiler-rt for this test

Re: [lldb-dev] [cfe-dev] [8.0.0 Release] rc5 has been tagged

On 12 Mar 2019, at 12:16, Hans Wennborg via cfe-dev wrote: > 8.0.0-rc5 was just tagged from the release_80 branch at r355909. > > This is identical to rc4 with the addition of r355743. Hopefully it is the > final release candidate, so please give it a good testing. Again, I had to disable comp

Re: [lldb-dev] [Release-testers] [8.0.0 Release] The final tag is in

On 18 Mar 2019, at 14:04, Hans Wennborg via Release-testers wrote: > The final version of 8.0.0 was just tagged from the release_80 branch > at r356364. It's identical to rc5 except for a few documentation > changes. Again, I had to disable compiler-rt for this test run, as most of the sanitize

Re: [lldb-dev] [Release-testers] Release 7.1.0 -rc1 has been tagged

On 27 Mar 2019, at 22:27, Tom Stellard via Release-testers wrote: > > I've just tagged 7.1.0-rc1. Testers, please begin testing and reporting > results. Main test results on amd64-freebsd11: Expected Passes: 52441 Expected Failures : 232 Unsupported Tests : 3687 Unexpected Passe

Re: [lldb-dev] [Release-testers] LLVM 7.1.0-final has been tagged

On 12 Apr 2019, at 02:00, Tom Stellard via Release-testers wrote: > > I've just tagged LLVM 7.1.0-final. Testers, please upload the final binaries. Unfortunately in the 7.x branch, r345199 was not merged, which reverted commits r333103 ("Teach __libcpp_is_floating_point that __fp16 and _Float

Re: [lldb-dev] [Release-testers] LLVM 8.0.1-rc2 has been tagged

On 11 Jun 2019, at 05:53, Tom Stellard via Release-testers wrote: > > I've tagged the 8.0.1-rc2 release, testers please begin testing and upload > your > binaries. As with 8.0.1 rc1, I had to disable compiler-rt for this test run, as most of the sanitizers are totally broken. This is tracked

Re: [lldb-dev] [Release-testers] LLVM 8.0.1-rc3

On 28 Jun 2019, at 00:56, Tom Stellard via Release-testers wrote: > > I've just tagged LLVM 8.0.1-rc3. Testers, please begin testing and report > results. As with 8.0.1 rc2, I had to disable compiler-rt for this test run, as most of the sanitizers are totally broken. This is tracked in PR4076

Re: [lldb-dev] [cfe-dev] [Release-testers] LLVM 8.0.1-rc3

On 6 Jul 2019, at 04:36, Christian Gagneraud wrote: > > On Thu, 4 Jul 2019 at 22:16, Yvan Roux via cfe-dev > wrote: >>> Expected Passes: 53266 (rc2: 53259) >>> Expected Failures : 213 (rc2: 213) >>> Unsupported Tests : 1718 (rc2: 1719) >>> Unresolved Tests : 8 (rc2: 8) > >

Re: [lldb-dev] [Release-testers] 8.0.1-rc4 release has been tagged.

On 11 Jul 2019, at 05:24, Tom Stellard via Release-testers wrote: > > I've tagged the 8.0.1-rc4 release, please begin testing. This will > (hopefully) > be the last release candidate. If all goes well, I will tag the final release > next Wednesday. As with 8.0.1 rc3, I had to disable compile

Re: [lldb-dev] [Release-testers] 8.0.1-final has been tagged

On 20 Jul 2019, at 05:21, Tom Stellard via Release-testers wrote: > The 8.0.1 final release has been tagged. Testers please upload the final > binaries. As with 8.0.1 rc4, I had to disable compiler-rt for this test run, as most of the sanitizers are totally broken. This is tracked in PR40761.

Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 1 is here

On 29 Jul 2019, at 16:32, Hans Wennborg via Release-testers wrote: > > 9.0.0-rc1 was just tagged from the release_90 branch at r367217 > (tagged as llvmorg-9.0.0-rc1 in the Git monorepo). The sanitizer tests went a lot better now, thanks to Alexander Richardson's patches in https://bugs.llvm.o

Re: [lldb-dev] [cfe-dev] [Release-testers] [9.0.0 Release] Release Candidate 1 is here

On 2019-08-06 22:59, Marshall Clow wrote: > Many of the failing libc++ tests are explicitly XFAILed for NetBSD; I wonder > if they should also be for FreeBSD. If they can't be fixed, then indeed they should be XFAILed. But maybe not right away, see below. >libcxx/thread/thread.threads/thr

Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 2 is here

On 14 Aug 2019, at 10:14, Hans Wennborg via Release-testers wrote: > > 9.0.0-rc2 was tagged yesterday from the release_90 branch at r368683. > In the Git monorepo it's available as the llvmorg-9.0.0-rc2 tag. For this rc, I only needed one patch, from: * https://bugs.llvm.org/show_bug.cgi?id=42

Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 3 is here

On 30 Aug 2019, at 18:38, Hans Wennborg via Release-testers wrote: > > 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In > the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. For this rc, I used two patches, from: * https://bugs.llvm.org/show_bug.cgi?id=42892 - After r356631

Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 4 is here

On 10 Sep 2019, at 12:26, Hans Wennborg via Release-testers wrote: > > 9.0.0-rc4 was just tagged from the release_90 branch at r371490. In > the Git monorepo, it's tagged as llvmorg-9.0.0-rc4. For this rc, I used two patches, from: * https://bugs.llvm.org/show_bug.cgi?id=42892 - After r356631,

Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 5 is here

On 13 Sep 2019, at 14:06, Hans Wennborg via Release-testers wrote: > > 9.0.0-rc5 was just tagged from the release_90 branch at r371837. In > the Git monorepo, it's tagged as llvmorg-9.0.0-rc5. For this rc, I used two patches, from: * https://bugs.llvm.org/show_bug.cgi?id=42892 - After r356631,

Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 6 is here

On 19 Sep 2019, at 16:51, Hans Wennborg via Release-testers wrote: > > On Tue, Sep 17, 2019 at 4:05 PM Hans Wennborg wrote: >> >> 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In >> the Git monorepo, it's tagged as llvmorg-9.0.0-rc6. > > This has now been tagged as the fina

Re: [lldb-dev] [Release-testers] LLVM 9.0.1-rc1 Release has been tagged

On 23 Nov 2019, at 07:20, Tom Stellard via Release-testers wrote: > > I've tagged the LLVM 9.0.1-rc1 release. Testers can begin testing and upload > binaries. I've also updated the test-release.sh script to pull from GitHub > instead of SVN, if you run into any issues with the new script, let

Re: [lldb-dev] [Release-testers] LLVM 9.0.1-rc2 has been tagged

On 7 Dec 2019, at 04:03, Tom Stellard via Release-testers wrote: > I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. > If all goes well, this will be the last -rc. For this rc, I used two patches, from: * https://bugs.llvm.org/show_bug.cgi?id=42892 - After r356631,

Re: [lldb-dev] [Release-testers] LLVM 9.0.1-rc3 has been tagged

On 14 Dec 2019, at 07:34, Tom Stellard via Release-testers wrote: > > I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading > binaries. This will be the last release candidate unless there is a > major problem. I'm planning to tag the final release on Dec 19. For this rc,

Re: [lldb-dev] [Release-testers] LLVM 9.0.1-rc3 has been tagged

On 19 Dec 2019, at 23:51, Tom Stellard wrote: > > On 12/16/2019 10:30 AM, Dimitry Andric wrote: >> On 14 Dec 2019, at 07:34, Tom Stellard via Release-testers >> wrote: >>> >>> I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading >>> binaries. This will be the last release

Re: [lldb-dev] [Release-testers] LLVM 9.0.1-final has been tagged

On 20 Dec 2019, at 05:06, Tom Stellard via Release-testers wrote: > > I've just tagged the 9.0.1-final release. Testers can begin uploading > binaries. For the final build, I used two patches, from: * https://bugs.llvm.org/show_bug.cgi?id=42892 - After r356631, Sanitizer-i386-Test faills to

Re: [lldb-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers wrote: > > It took a bit longer than planned due to master being a somewhat > unstable at the branch point, but Release Candidate 1 has now been > tagged as llvmorg-10.0.0-rc1. For this rc, I used three patches, which are attached. Ma

Re: [lldb-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On 3 Feb 2020, at 10:57, Hans Wennborg wrote: > > On Fri, Jan 31, 2020 at 9:37 PM Dimitry Andric wrote: ... >> Unfortunately the test-suite did not build at all, as all the Bitcode >> compilations failed with segfaults, similar to the following run under >> gdb: >> >> Starting program: >> /hom

Re: [lldb-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers wrote: > > It took a bit longer than planned due to master being a somewhat > unstable at the branch point, but Release Candidate 1 has now been > tagged as llvmorg-10.0.0-rc1. I tried building rc1 for 32-bit FreeBSD, but ran into a co

Re: [lldb-dev] [Release-testers] [10.0.0 Release] Release Candidate 1 is here

On 4 Feb 2020, at 12:06, Dimitry Andric via Release-testers wrote: > > On 30 Jan 2020, at 20:38, Hans Wennborg via Release-testers > wrote: >> >> It took a bit longer than planned due to master being a somewhat >> unstable at the branch point, but Release Candidate 1 has now been >> tagged as

Re: [lldb-dev] [Release-testers] [cfe-dev] [10.0.0 Release] Release Candidate 1 is here

On 6 Feb 2020, at 11:16, Yvan Roux via Release-testers wrote: ... > And a bunch of errors in the testsuite: > > FAILED: > Bitcode/simd_ops/CMakeFiles/simd_ops_test_op_usubl_1306.dir/AArch64_halide_runtime.bc.o > /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/test-suite-

Re: [lldb-dev] [Release-testers] [10.0.0 Release] Release Candidate 2 is here

On 13 Feb 2020, at 23:34, Hans Wennborg via Release-testers wrote: > > Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It > includes 98 commits since the previous release candidate. For this rc, I used three patches, which are attached. Main results on amd64-freebsd11: E

Re: [lldb-dev] [Release-testers] [10.0.0 Release] Release Candidate 4 is here

On 13 Mar 2020, at 20:09, Hans Wennborg via Release-testers wrote: > > Release Candidate 4 was tagged earlier today as llvmorg-10.0.0-rc4 on > the release branch at b406eab8880. It contains 12 commits since the > previous release candidate. For 10.0.0-rc4, I used three patches, which are attach

Re: [lldb-dev] [Release-testers] [10.0.0 Release] Release Candidate 4 is here

On 15 Mar 2020, at 10:58, Dimitry Andric via Release-testers wrote: > > On 13 Mar 2020, at 20:09, Hans Wennborg via Release-testers > wrote: >> >> Release Candidate 4 was tagged earlier today as llvmorg-10.0.0-rc4 on >> the release branch at b406eab8880. It contains 12 commits since the >> pr

Re: [lldb-dev] [Release-testers] [10.0.0 Release] Release Candidate 5 is here

On 19 Mar 2020, at 14:51, Hans Wennborg via Release-testers wrote: > > I had hoped that rc4 would be the last one, but I wanted to pick up > one more fix, so here we go. > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > release branch at 35627038123. For 10.0.0-rc5, I used

Re: [lldb-dev] [Release-testers] LLVM 10.0.0 Release

On 24 Mar 2020, at 21:32, Hans Wennborg via Release-testers wrote: > > I am pleased to announce that LLVM 10 is now available. > > Get it here: https://llvm.org/releases/download.html#10.0.0 For 10.0.0-final, I used three patches, which are attached. Main results on amd64-freebsd11: Expect

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Since Bugzilla numbers are all under 50,000 (at least for now:), can't we simply bump the GitHub issue/pull request numbers to 50,000, and start from there? Then it would be easy to identify: < 5 means Bugzilla, >= 5 means GitHub. Now somebody's only gotta find a way to file 5-200

Re: [lldb-dev] [Release-testers] 10.0.1-rc1 release has been tagged

On 20 May 2020, at 03:22, Tom Stellard via Release-testers wrote: > > I have just tagged the 10.0.1-rc1 release. Testers can begin testing and > uploading > binaries. > > If you still want to get a fix into the 10.0.1 release, you still have about > a month > to get your fix in. To request

  1   2   >