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

[Brian Cain via lldb-dev]

On Mon, Sep 20, 2021 at 1:14 PM Andrzej Warzynski 
wrote:

> Hi Brian,
>
> Thank you for helping with the release!
>
> On 20/09/2021 18:40, Brian Cain via Openmp-dev wrote:
> > I also disabled flang (-no-flang) because of
> > memory exhaustion while trying to build.  Is this increased memory
> > consumption expected or could it be a bug?
>
> The memory usage of LLVM Flang was discussed in the past:
> * https://bugs.llvm.org/show_bug.cgi?id=50059
> * https://lists.llvm.org/pipermail/flang-dev/2019-November/61.html
>
> It's not great, but sadly it is rather unlikely to improve in the near
> future.
>
>
Ok, I understand.  I am not opposed to including flang in this build, if I
can get it to work.  Is there a way to set some kind of variable to limit
the concurrency for building (only) these targets?  Like
LLVM_PARALLEL_LINK_JOBS works today.  What if test-release.sh defined
LLVM_PARALLEL_FLANG_COMPILE_JOBS to "1" (or I defined it in
-configure-flags) and there were some cmake magic that handled that input
to control how the build were invoked?  I think that would be a good
workaround.



> Thanks,
> -Andrzej
>
> >
> > $ cat clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256
> > 488ff13c9a54f6b7b2aeb26e930da7d72e32a15542929cd642fc0b7d37e79967
> >   clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz
> >
> > On Mon, Sep 13, 2021 at 11:40 PM Tom Stellard via Release-testers
> > mailto:release-test...@lists.llvm.org>>
>
> > wrote:
> >
> > Hi,
> >
> > I've tagged 13.0.0-rc3.  This will likely be the last rc unless
> > there are
> > critical bugs that are found.  Please test the release and report
> > results.
> >
> > -Tom
> >
> > ___
> > Release-testers mailing list
> > release-test...@lists.llvm.org  release-test...@lists.llvm.org>
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
> > 
> >
> >
> >
> > --
> > -Brian
> >
> > ___
> > Openmp-dev mailing list
> > openmp-...@lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
> >
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Ubuntu 20 binary uploaded.  I also disabled flang (-no-flang) because of
memory exhaustion while trying to build.  Is this increased memory
consumption expected or could it be a bug?

$ cat clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256

488ff13c9a54f6b7b2aeb26e930da7d72e32a15542929cd642fc0b7d37e79967
 clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz

On Mon, Sep 13, 2021 at 11:40 PM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've tagged 13.0.0-rc3.  This will likely be the last rc unless there are
> critical bugs that are found.  Please test the release and report results.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [llvm-dev] Mailing List Status Update

[Brian Cain via lldb-dev]

On Mon, Jun 21, 2021 at 3:16 PM Kevin P. Neal via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> On Mon, Jun 21, 2021 at 12:58:22PM -0700, David Blaikie via cfe-dev wrote:
> >>On Mon, Jun 21, 2021 at 12:53 PM Chris Lattner via cfe-dev
> >><[1]cfe-...@lists.llvm.org> wrote:
> >>
> >>Hi Philip,
> >>First, despite the similar names, Discord is very different than
> >>Discourse.  Here Iâm only commenting about Discourse, I have no
> >>opinion about Discord.
> >>In this case, I think we need to highly weight the opinions of the
> >>people actively mainlining the existing systems.  It has become
> clear
> >>that the priority isnât âcontrol our own listsâ, it is âmake sure
> they
> >>stay upâ and âget LLVM people out of maintaining themâ.
> >>The ongoing load of maintaining these lists (including moderation)
> and
> >>of dealing with the security issues that keep coming up are carried
> by
> >>several individuals, not by the entire community.  Iâm concerned
> about
> >>those individuals, but Iâm also more broadly concerned about *any*
> >>individuals being solely responsible for LLVM infra.  Effectively
> >>every case weâve had where an individual has driving LLVM infra turns
> >>out to be a problem.  LLVM as a project isnât good at running web
> >>scale infra, but we highly depend on it.
> >>It seems clear to me that we should outsource this to a proven
> >>vendor.  Your concerns about discourse seem very similar to the
> >>discussion about moving to Github (being a single vendor who was once
> >>much smaller than Microsoft).  I think your concerns are best
> >>addressed by having the IWG propose an answer to âwhat is our plan if
> >>Discourse-the-company goes sideways?"
>
> >Might also be worth some details on: "Why is Discourse more suitable
> >than a hosted mailman solution?" - if the main goal is to get LLVM
> >individual contributors out of maintaining infrastructure, moving to a
> >hosted version of the current solution seems lower friction/feature
> >creep/etc? (though I realize moving between solutions is expensive,
> and
> >it may be worthwhile gaining other benefits that Discourse may provide
> >while we address the original/motivating issue of maintenance)Â
>
> I notice that Discord gets maybe 50-100 messages a day, IRC perhaps a
> little less, but Discourse gets almost none. It's a very low daily number.
> The mailing lists that I'm on (just clang and llvm) get 500+ messages a
> day.
>
> Are we really going to replace email with Discourse when we can see that
> almost nobody likes using Discourse?
>
>
>
Metcalfe's law - people are going to tend to use the medium that they are
able to reach the audience on, but not necessarily because it's superior.
Mailing lists have the benefit of long-term incumbency.

I think I would prefer maintaining the status quo but if I woke up tomorrow
and the conversation had moved to Discourse I would join it there.
Regardless of whether it had moved by mandate or popular adoption.  I
suspect others may feel similar and therefore the traffic is not a good
metric of preference.

-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

SLES12, Ubuntu 16.04 uploaded - now to the correct path - thanks for the
reminder, Hans!

e96a6402cc139323d64e20570c63b7e8c5d442e7338a1cae6c3234db06431883
 clang+llvm-12.0.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz
dc498c1caabc57ae94b191fbcb887d7a557279f3eecb2206dbdd3ede5793dc98
 clang+llvm-12.0.0-rc3-x86_64-linux-sles12.4.tar.xz

On Thu, Mar 11, 2021 at 11:23 PM Brian Cain  wrote:

> Uploaded SLES12 but I did encounter the same ENOSPC that others have
> reported.
>
> $ cat clang+llvm-12.0.0-rc3-x86_64-linux-sles12.4.tar.xz.sha256
> dc498c1caabc57ae94b191fbcb887d7a557279f3eecb2206dbdd3ede5793dc98
>  clang+llvm-12.0.0-rc3-x86_64-linux-sles12.4.tar.xz
>
> On Thu, Mar 11, 2021 at 4:27 PM Brian Cain  wrote:
>
>> lit tests require python 3.6 now but CMake nor test-release.sh screen for
>> this.  It's definitely a nice-to-have, though.
>>
>> Older platforms like SLES12 and Ubuntu Xenial don't have a native 3.6.
>> I'll add a local python build to get the test suite going.
>>
>> Apologies -- I realize it's not as helpful for me to offer feedback this
>> late in the release cycle.
>>
>> On Wed, Mar 10, 2021 at 9:11 AM Tom Stellard via Release-testers <
>> release-test...@lists.llvm.org> wrote:
>>
>>> Hi,
>>>
>>> I've tagged LLVM 12.0.0-rc3.  Testers may begin testing and uploading
>>> binaries.
>>> If all goes well, this will be the last RC.
>>>
>>> -Tom
>>>
>>> ___
>>> Release-testers mailing list
>>> release-test...@lists.llvm.org
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>>>
>>
>>
>> --
>> -Brian
>>
>
>
> --
> -Brian
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Attempted upload of Ubuntu 16.04 (below), but it too ran out of space.
Maybe I'm copying to the wrong remote path?  Dimitry, how did you get your
upload to work?

e96a6402cc139323d64e20570c63b7e8c5d442e7338a1cae6c3234db06431883
 clang+llvm-12.0.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz

On Thu, Mar 11, 2021 at 11:23 PM Brian Cain  wrote:

> Uploaded SLES12 but I did encounter the same ENOSPC that others have
> reported.
>
> $ cat clang+llvm-12.0.0-rc3-x86_64-linux-sles12.4.tar.xz.sha256
> dc498c1caabc57ae94b191fbcb887d7a557279f3eecb2206dbdd3ede5793dc98
>  clang+llvm-12.0.0-rc3-x86_64-linux-sles12.4.tar.xz
>
> On Thu, Mar 11, 2021 at 4:27 PM Brian Cain  wrote:
>
>> lit tests require python 3.6 now but CMake nor test-release.sh screen for
>> this.  It's definitely a nice-to-have, though.
>>
>> Older platforms like SLES12 and Ubuntu Xenial don't have a native 3.6.
>> I'll add a local python build to get the test suite going.
>>
>> Apologies -- I realize it's not as helpful for me to offer feedback this
>> late in the release cycle.
>>
>> On Wed, Mar 10, 2021 at 9:11 AM Tom Stellard via Release-testers <
>> release-test...@lists.llvm.org> wrote:
>>
>>> Hi,
>>>
>>> I've tagged LLVM 12.0.0-rc3.  Testers may begin testing and uploading
>>> binaries.
>>> If all goes well, this will be the last RC.
>>>
>>> -Tom
>>>
>>> ___
>>> Release-testers mailing list
>>> release-test...@lists.llvm.org
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>>>
>>
>>
>> --
>> -Brian
>>
>
>
> --
> -Brian
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded SLES12 but I did encounter the same ENOSPC that others have
reported.

$ cat clang+llvm-12.0.0-rc3-x86_64-linux-sles12.4.tar.xz.sha256
dc498c1caabc57ae94b191fbcb887d7a557279f3eecb2206dbdd3ede5793dc98
 clang+llvm-12.0.0-rc3-x86_64-linux-sles12.4.tar.xz

On Thu, Mar 11, 2021 at 4:27 PM Brian Cain  wrote:

> lit tests require python 3.6 now but CMake nor test-release.sh screen for
> this.  It's definitely a nice-to-have, though.
>
> Older platforms like SLES12 and Ubuntu Xenial don't have a native 3.6.
> I'll add a local python build to get the test suite going.
>
> Apologies -- I realize it's not as helpful for me to offer feedback this
> late in the release cycle.
>
> On Wed, Mar 10, 2021 at 9:11 AM Tom Stellard via Release-testers <
> release-test...@lists.llvm.org> wrote:
>
>> Hi,
>>
>> I've tagged LLVM 12.0.0-rc3.  Testers may begin testing and uploading
>> binaries.
>> If all goes well, this will be the last RC.
>>
>> -Tom
>>
>> ___
>> Release-testers mailing list
>> release-test...@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>>
>
>
> --
> -Brian
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

lit tests require python 3.6 now but CMake nor test-release.sh screen for
this.  It's definitely a nice-to-have, though.

Older platforms like SLES12 and Ubuntu Xenial don't have a native 3.6.
I'll add a local python build to get the test suite going.

Apologies -- I realize it's not as helpful for me to offer feedback this
late in the release cycle.

On Wed, Mar 10, 2021 at 9:11 AM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've tagged LLVM 12.0.0-rc3.  Testers may begin testing and uploading
> binaries.
> If all goes well, this will be the last RC.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Ubuntu16 uploaded:

$ cat clang+llvm-11.1.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
c691a558967fb7709fb81e0ed80d1f775f4502810236aa968b4406526b43bee1
 clang+llvm-11.1.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz


On Wed, Feb 17, 2021 at 10:06 PM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've tagged 11.1.0-final, testers may begin uploading binaries now.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded x86_64 Ubuntu 16.04:

$ cat clang+llvm-11.1.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
3299ea97ed2bb9f6d583e718573d2153491a984ee5401c01e994f3fb98b0d607
 clang+llvm-11.1.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz

On Mon, Feb 8, 2021 at 11:15 AM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've tagged LLVM 11.1.0-rc3.  If there are no issues, then I'll be tagging
> the final release in 1 week.  Testers please test and upload binaries.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded Ubuntu 16, SLES12.

 $ cat clang+llvm-11.0.1-x86_64-linux-sles12.4.tar.xz.sha256
clang+llvm-11.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
77cd59cf6f932cf2b3c9a68789d1bd3f7ba9f471a28f6ba25e25deb1a0806e0d
 clang+llvm-11.0.1-x86_64-linux-sles12.4.tar.xz
67f18660231d7dd09dc93502f712613247b7b4395e6f48c11226629b250b53c5
 clang+llvm-11.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz

On Tue, Jan 5, 2021 at 9:21 PM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've tagged LLVM 11.0.1-final.  Testers can upload the final binaries now.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded Ubuntu 16 and SLES12:

d2cdda0d8b1f4fe44eb8a7751e488b5601d820dc260e81c73b05b5725ea4ca6a
 clang+llvm-11.0.1-rc2-x86_64-linux-gnu-ubuntu-16.04.tar.xz
da035f77cf043fc0c31842b0e54c1c47d893895ac109b261c6d91ea8aeccabc1
 clang+llvm-11.0.1-rc2-x86_64-linux-sles12.4.tar.xz

On Sat, Dec 19, 2020 at 12:33 AM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've just tagged LLVM 11.0.1-rc2, hopefully this will be the last
> release candidate.  Testers can begin testing and uploading binaries.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded Ubuntu 16 tarball:

dcd37b46d2b3002d078ff38d967e674f4837090c4f61ee403f2cb0ada6a6dbd2
 clang+llvm-11.0.1-rc1-x86_64-linux-gnu-ubuntu-16.04.tar.xz

BTW - Neil -- if you decide to post binaries for Ubuntu 20, you should know
that there was a request in another thread to include LLDB in the ubuntu
packages.  The ubuntu binaries  I've made do include it (test-release takes
an "-lldb" arg).


On Thu, Nov 26, 2020 at 1:21 AM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've tagged LLVM 11.0.1-rc1.  Testers may begin testing and uploading
> binaries.  If you still have bugs you want fixed in LLVM 11.0.1, you
> have until Dec. 8 to request backports.  You can make these requests by
> filing a bug at bugs.llvm.org and putting release-11.0.1 in the 'blocks'
> field.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded binaries for SLES12 and Ubuntu 16 x86_64.  I realized that I'd
forgotten rc3,4 ones so I uploaded them too.

$ cat clang+llvm-11.0.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
clang+llvm-11.0.0-rc3-x86_64-linux-sles12.4.tar.xz.sha256
clang+llvm-11.0.0-rc4-x86_64-linux-sles12.4.tar.xz.sha256
clang+llvm-11.0.0-rc5-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
clang+llvm-11.0.0-rc5-x86_64-linux-sles12.4.tar.xz.sha256

aaf668664769dfb071c59f5d2622f3459d457b58489ee79f69262cef8cf2abb4
 clang+llvm-11.0.0-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz
93394ee58b18ec72bf4455dc6055a9ba5100621282547c686bd4ef689fe1d8a5
 clang+llvm-11.0.0-rc3-x86_64-linux-sles12.4.tar.xz
91a0984c7d0be93af310a1d762e34e283952ce9734ecec040b6a90fd31466150
 clang+llvm-11.0.0-rc4-x86_64-linux-sles12.4.tar.xz
af8daead4a6d996fab7630759a9330d5eb0ceea06dbd6daa7fdd92126b0f02ee
 clang+llvm-11.0.0-rc5-x86_64-linux-gnu-ubuntu-16.04.tar.xz
b57ef3689a6bf161dab3fee644fe0837e1c9cb31875556f7be259b8eaf64a43d
 clang+llvm-11.0.0-rc5-x86_64-linux-sles12.4.tar.xz



On Wed, Sep 30, 2020 at 1:07 PM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hello again,
>
> We had to pick up another bug fix, so here is another release
> candidate: llvmorg-11.0.0-rc5 tag was just created.
>
> Source code and docs are available at
> https://prereleases.llvm.org/11.0.0/#rc5
> and
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc5
>
> Pre-built binaries will be added as they become ready.
>
> Please file reports for any bugs you find as blockers of
> https://llvm.org/pr46725
>
> Release testers, if you still have cycles (perhaps you didn't even
> have time to start rc4 yet), please run the test script, share your
> results, and upload binaries.
>
> As mentioned above, this rc is very similar to the previous one. There
> are no open blockers, so it could be the last release candidate.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [11.0.0 Release] Release Candidate 2 is here

[Brian Cain via lldb-dev]

Uploaded Ubuntu 16 and SLES12 binaries:

$ cat clang+llvm-11.0.0-rc2-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
clang+llvm-11.0.0-rc2-x86_64-linux-sles12.4.tar.xz.sha256
051d288dfc6ef9ff8e37d97b722695390427c617d3b538a93f2d0d413fb6f54a
 clang+llvm-11.0.0-rc2-x86_64-linux-gnu-ubuntu-16.04.tar.xz
5d1a54fbca4e3c9865094c8c4602d5761adc49a1f4c58d2a481cbe502ea35f74
 clang+llvm-11.0.0-rc2-x86_64-linux-sles12.4.tar.xz

On Thu, Aug 20, 2020 at 3:34 PM Hans Wennborg via llvm-dev <
llvm-...@lists.llvm.org> wrote:

> Hello everyone,
>
> The llvmorg-11.0.0-rc2 tag was just created.
>
> Source code and docs are available at
> https://prereleases.llvm.org/11.0.0/#rc2 and
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc2
>
> Pre-built binaries will be added as they become ready.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr46725
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
>
> We're a bit behind schedule, but I also don't think we have any super
> bad bugs open, so hopefully we can still wrap up fairly soon.
>
> Thanks,
> Hans
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded sles12, ubuntu16:

 $ cat clang+llvm-10.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
48b83ef827ac2c213d5b64f5ad7ed082c8bcb712b46644e0dc5045c6f462c231
 clang+llvm-10.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz

$ cat clang+llvm-10.0.1-x86_64-linux-sles12.4.tar.xz.sha256
59f35fc7967b740315edf31a54b228ae5da8a54f499e37d424d67b7107217ae4
 clang+llvm-10.0.1-x86_64-linux-sles12.4.tar.xz

On Tue, Jul 21, 2020 at 12:25 AM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've tagged 10.0.1-final.  Testers, please begin uploading your binaries.
>
> Thanks,
> Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] 10.0.1-rc4 tagged

[Brian Cain via lldb-dev]

Uploaded:
dcf43e25a77a2ffb4ffaa5a04babe409b2b3ffac07bc989a1dca730ecacb43c2
 clang+llvm-10.0.1-rc4-x86_64-linux-sles12.4.tar.xz
6db54d9f55fb41877b23f4b89e7b68d44fcc5378d615d232c820307237dc33f7
 clang+llvm-10.0.1-rc2-x86_64-linux-sles12.4.tar.xz
2d907945d8d8d5d2969c6947c50d91e100d5dd09ccb37214a811c11cbfa635af
 clang+llvm-10.0.1-rc3-x86_64-linux-sles12.4.tar.xz

ccdfda65932661e5fd4faba1fde17fe3800f39b4c21687242b7cdfdbea4cf131
 clang+llvm-10.0.1-rc3-x86_64-linux-gnu-ubuntu-16.04.tar.xz
761a6f4658545f733f14dcd6c50a16b49994a4c448c779616c5716eed80b90f1
 clang+llvm-10.0.1-rc4-x86_64-linux-gnu-ubuntu-16.04.tar.xz

I saw phase2/3 mismatches that seem concerning.  Are these the only
platforms that encountered them?

I can open a bug, let me know if there's particular data beyond the logs I
should gather.


On Tue, Jul 7, 2020 at 11:08 PM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've tagged 10.0.1-rc4, please test and report the results.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [10.0.0 Release] Release Candidate 3 is here

[Brian Cain via lldb-dev]

Uploaded Ubuntu 18.04 binaries:
7ebc00479d05772e56c34c1b0f40295af2dd4a6b165d9107946ff2cdb7c219ac
 clang+llvm-10.0.0-rc3-x86_64-linux-gnu-ubuntu-18.04.tar.xz

On Wed, Mar 4, 2020 at 7:49 AM Hans Wennborg via llvm-dev <
llvm-...@lists.llvm.org> wrote:

> Hello everyone,
>
> It took a bit longer than planned, but Release Candidate 3 is now
> here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at
> 3a843031a5 and contains 95 commits since the previous release
> candidate.
>
> If no new problems arise, this is what the final release will look like.
>
> Source code and docs are available at
> https://prereleases.llvm.org/10.0.0/#rc3 and
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc3
>
> Pre-built binaries will be added as they become ready.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
>
> Release testers, please run the test script, share your results, and
> upload binaries.
>
> Thanks,
> Hans
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded ubuntu 18 binaries.

$ cat clang+llvm-10.0.0-rc2-x86_64-linux-gnu-ubuntu-18.04.tar.xz.sha256
8ca2cd0e0ba2243c095134373b46ccad822192b0495ce13eb0af33e12f9d17e1
 clang+llvm-10.0.0-rc2-x86_64-linux-gnu-ubuntu-18.04.tar.xz

On Thu, Feb 13, 2020 at 4:34 PM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hello everyone,
>
> Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It
> includes 98 commits since the previous release candidate.
>
> Source code and docs are available at
> https://prereleases.llvm.org/10.0.0/#rc2 and
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc2
>
> Pre-built binaries will be added as they become available.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr44555
>
> Release testers: please run the test script, share your results, and
> upload binaries.
>
> I'm hoping we can now start tying up the loose ends, fixing the
> blocking bugs, and getting the branch ready for shipping as a stable
> release soon.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

On Thu, Jan 9, 2020 at 12:29 AM Tom Stellard  wrote:

> On 01/08/2020 09:24 AM, Brian Cain wrote:
> > Tom, the 9.0.1 final binaries didn't (yet?) make it to the github
> release page
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1
> >
>
> The binaries have been posted now.
>
>
I don't see the ubuntu 16 one that I uploaded there -
clang+llvm-9.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz



> > I also checked https://releases.llvm.org/ because I recall some debate
> or back-and-forth about where the releases should go and/or redirects or
> links from one to the other.  But they're not there either.
> >
>
> I'm working on fixing the releases.llvm.org page.
>
> -Tom
>
> > On Thu, Dec 19, 2019 at 10:07 PM Tom Stellard via cfe-dev <
> cfe-...@lists.llvm.org > wrote:
> >
> > Hi,
> >
> > I've just tagged the 9.0.1-final release.  Testers can begin
> uploading binaries.
> >
> > -Tom
> >
> > ___
> > cfe-dev mailing list
> > cfe-...@lists.llvm.org 
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
> >
> >
> >
> > --
> > -Brian
>
>

-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Tom, the 9.0.1 final binaries didn't (yet?) make it to the github release
page https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1

I also checked https://releases.llvm.org/ because I recall some debate or
back-and-forth about where the releases should go and/or redirects or links
from one to the other.  But they're not there either.

On Thu, Dec 19, 2019 at 10:07 PM Tom Stellard via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> Hi,
>
> I've just tagged the 9.0.1-final release.  Testers can begin uploading
> binaries.
>
> -Tom
>
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded Ubuntu 16.

608285fb0503ee6d15ce9acb8f4575bba4d78e06
 clang+llvm-9.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz

On Thu, Dec 19, 2019 at 10:07 PM Tom Stellard via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> Hi,
>
> I've just tagged the 9.0.1-final release.  Testers can begin uploading
> binaries.
>
> -Tom
>
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded ubuntu x86 binaries:

4361dc68e47b9972f0ec7db0c20411f60df90f28
 clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz
085f223d48fd6fcf372f54ccdf8bbac403c279a2
 clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz
b1627073e533975f0b4d4366b5f6e4dd44c7c6d8
 clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04.tar.xz

On Tue, Sep 17, 2019 at 9:05 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hello everyone,
>
> 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.
>
> Source code and docs are available at
> https://prereleases.llvm.org/9.0.0/#rc6
>
> This is the same as rc5 plus one very minor change (r371969) that
> still seemed good to pick up.
>
> I'm not allocating extra time for testing this one, expecting to tag
> 'final' in a day or two unless any new problem arises. If you still
> have cycles to spare, testing is still very much appreciated of
> course.
>
> As usual, please file bug reports about any issues you find, marking
> them blocking of https://llvm.org/PR42474
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded SLES11 and Ubuntu 16 binaries:

1c7895122974828c678f7059e0427d0228ab41e5
 clang+llvm-9.0.0-rc4-x86_64-linux-sles11.3.tar.xz
d23219bc416afdf2a7eff11490dfb497001dc3a4
 clang+llvm-9.0.0-rc4-x86_64-linux-gnu-ubuntu-16.04.tar.xz

On Tue, Sep 10, 2019 at 5:26 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hello again,
>
> 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.
>
> Source code and docs are available at
> https://prereleases.llvm.org/9.0.0/#rc4 Binaries will be added as they
> become available.
>
> There are not a lot of changes from rc3 to rc4, and there are again no
> open release blockers, so I'm hoping this will be the last release
> candidate and that we can tag the final release soon.
>
> Please file bug reports for any issues you find, marking them blocking
> of https://llvm.org/PR42474
>
> Release testers, please run the test script, share your results, and
> upload binaries.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Oh! Indeed, that was probably it. I'll try again.

On Tue, Aug 20, 2019, 5:26 AM Hans Wennborg  wrote:

> No, there should be no mismatch now. Maybe you ended up using a
> version of test-release.sh that doen't have the fixes?
>
> On Sun, Aug 18, 2019 at 6:47 PM Brian Cain  wrote:
> >
> > When I built rv2 for SLES11 linux I saw the same phase 2/3 mismatch.  Is
> that expected?
> >
> > On Wed, Aug 14, 2019, 3:15 AM Hans Wennborg via Release-testers <
> release-test...@lists.llvm.org> wrote:
> >>
> >> Hello everyone,
> >>
> >> 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.
> >>
> >> Source code and docs are available at
> https://prereleases.llvm.org/9.0.0/#rc2
> >>
> >> Binaries will be added as they become available.
> >>
> >> The tag went in roughly one week behind schedule (see "Upcoming
> >> Releases" at https://llvm.org), but there are still two weeks left to
> >> the planned release date.
> >>
> >> Please file bug reports for any issues you find and mark them blocking
> >> https://llvm.org/PR42474 Please also look at the blockers and see if
> >> there's anything you can help with -- there are several bugs which
> >> lack traction at the moment.
> >>
> >> Release testers: please start your engines, run the script, share your
> >> results, and upload binaries.
> >>
> >> Many thanks,
> >> Hans
> >> ___
> >> Release-testers mailing list
> >> release-test...@lists.llvm.org
> >> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

When I built rv2 for SLES11 linux I saw the same phase 2/3 mismatch.  Is
that expected?

On Wed, Aug 14, 2019, 3:15 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hello everyone,
>
> 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.
>
> Source code and docs are available at
> https://prereleases.llvm.org/9.0.0/#rc2
>
> Binaries will be added as they become available.
>
> The tag went in roughly one week behind schedule (see "Upcoming
> Releases" at https://llvm.org), but there are still two weeks left to
> the planned release date.
>
> Please file bug reports for any issues you find and mark them blocking
> https://llvm.org/PR42474 Please also look at the blockers and see if
> there's anything you can help with -- there are several bugs which
> lack traction at the moment.
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
>
> Many thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded Ubuntu 18.04 binaries:
190157033defcfc0796f06696a73979cb4201594
 clang+llvm-9.0.0-rc1-x86_64-linux-gnu-ubuntu-18.04.tar.xz

I had three phase 2/3 comparison failures, opened PR42855.

# Comparing Phase 2 and Phase 3 files
file MachO_x86_64.cpp.o differs between phase 2 and phase 3
file JITLinkGeneric.cpp.o differs between phase 2 and phase 3
file llvm-config.cpp.o differs between phase 2 and phase 3

On Mon, Jul 29, 2019 at 9:32 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi everyone,
>
> 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).
>
> Source code and docs are available at
> https://prereleases.llvm.org/9.0.0/#rc1
>
> Binaries will be added as they become available.
>
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/PR42474
>
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded SLES11.

a18ac0820acf7e4b19b917a143868a73ddb30a02
 clang+llvm-8.0.1-x86_64-linux-sles11.3.tar.xz

On Tue, Jul 23, 2019 at 10:10 AM Brian Cain  wrote:

> [previously I misdirected this message as a reply to the 9.0.0 thread, so
> I'm reproducing here just in case]
>
> Uploaded ubuntu 14.
>
> I had to kill some tests executing "lldb-vscode", they had been running
> for 12+ hours without completing.
>
> b57383860c7e4317b0194d1a91836e01bd637c95
>  clang+llvm-8.0.1-x86_64-linux-gnu-ubuntu-14.04.tar.xz
>
> On Fri, Jul 19, 2019 at 10:21 PM Tom Stellard via Release-testers <
> release-test...@lists.llvm.org> wrote:
>
>> Hi,
>>
>> The 8.0.1 final release has been tagged.  Testers please upload the final
>> binaries.
>>
>> -Tom
>> ___
>> Release-testers mailing list
>> release-test...@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>>
>
>
> --
> -Brian
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

[previously I misdirected this message as a reply to the 9.0.0 thread, so
I'm reproducing here just in case]

Uploaded ubuntu 14.

I had to kill some tests executing "lldb-vscode", they had been running for
12+ hours without completing.

b57383860c7e4317b0194d1a91836e01bd637c95
 clang+llvm-8.0.1-x86_64-linux-gnu-ubuntu-14.04.tar.xz

On Fri, Jul 19, 2019 at 10:21 PM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> The 8.0.1 final release has been tagged.  Testers please upload the final
> binaries.
>
> -Tom
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [9.0.0 Release] The release branch is open; trunk is now 10.0.0

[Brian Cain via lldb-dev]

Uploaded ubuntu 14.

I had to kill some tests executing "lldb-vscode", they had been running for
12+ hours without completing.

b57383860c7e4317b0194d1a91836e01bd637c95
 clang+llvm-8.0.1-x86_64-linux-gnu-ubuntu-14.04.tar.xz

On Thu, Jul 18, 2019 at 7:19 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hello everyone,
>
> The release branch for LLVM 9 and its sub-projects was just created
> from trunk at r366426, and the trunk version was subsequently bumped
> to 10.0.0.
>
> Release blockers are tracked by https://llvm.org/PR42474 Please mark
> any bugs, old or new, that need to be fixed before the release as
> blocking that.
>
> To get a change committed to the branch, first commit it to trunk as
> usual, and then request it to be merged --- ideally by filing a
> blocker bug on https://llvm.org/PR42474, or by cc'ing me on the commit
> email. (Please don't request merges over IRC; there's a high risk I'll
> miss them.)
>
> Please help with the release by notifying me about any bugs, commits,
> or other issues you think might be relevant. If it's not already
> tracked as a blocker of the release bug, or I'm not cc'd on an email
> about it, I will probably miss it.
>
> When the branch is in good enough shape, hopefully by tomorrow, the
> first release candidate (RC1) will be tagged and testing can begin.
> The release schedule can be found under "Upcoming Releases" to the
> right at https://llvm.org
>
> Many thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

I noticed tests that didn't terminate on ubuntu-14.04 x86_64.  Is PR40761
gating this release?

On Fri, Jul 12, 2019 at 2:21 PM Dimitry Andric via Release-testers <
release-test...@lists.llvm.org> wrote:

> On 11 Jul 2019, at 05:24, Tom Stellard via Release-testers <
> release-test...@lists.llvm.org> 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 compiler-rt for this test run, as most
> of the sanitizers are totally broken. This is tracked in PR40761.
>
> Main test results on amd64-freebsd11:
>
> Expected Passes: 53262 (rc3: 53266)
> Passes With Retry  : 1 (rc3: 0)
> Expected Failures  :   213 (rc3:   213)
> Unsupported Tests  :  1718 (rc3:  1718)
> Unresolved Tests   : 8 (rc3: 8)
> Unexpected Passes  : 3 (rc3: 3)
> Unexpected Failures:62 (rc3:59)
>
> Main test results on i386-freebsd11:
>
> Expected Passes: 53114 (rc3: 53113)
> Passes With Retry  : 1 (rc3: 0)
> Expected Failures  :   229 (rc3:   229)
> Unsupported Tests  :  1540 (rc3:  1540)
> Unresolved Tests   : 8 (rc3: 7)
> Unexpected Passes  : 5 (rc3: 5)
> Unexpected Failures:   175 (rc3:   178)
>
> Uploaded:
>
> SHA256 (clang+llvm-8.0.1-rc4-amd64-unknown-freebsd11.tar.xz) =
> ffd4546aab6d7944b4063a8fd9f4022be8b4904760becc76ee2ea64d3fa50d7e
> SHA256 (clang+llvm-8.0.1-rc4-i386-unknown-freebsd11.tar.xz) =
> 52ab6fa940a4143c1ac2fc50f2aa0994b92a56fbf7d8b1146b74a7c5de743607
>
> -Dimitry
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded Ubuntu 14 and SLES 11 x86 binaries.

8a5d880f3ed2b10d80660d1029b0c958878c3cb7
clang+llvm-7.1.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz
81f5b08cc8cac534e4a7405de46a2ef28d978477
clang+llvm-7.1.0-x86_64-linux-sles11.3.tar.xz


On Thu, Apr 11, 2019 at 7:00 PM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've just tagged LLVM 7.1.0-final.  Testers, please upload the final
> binaries.
>
> Thanks,
> Tom
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Reminder: Austin LLVM Social is today, at The Tavern

[Brian Cain via lldb-dev]

See you at The Tavern tonight at 6pm!

922 W 12th St, Austin, TX 78703
https://www.tavernaustin.com/

-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] NEW LOCATION - Re: April LLVM Austin social is this Thursday!

[Brian Cain via lldb-dev]

Update: we will meet instead at "The Tavern":

922 W 12th St, Austin, TX 78703
https://www.tavernaustin.com/

11 April, 6:00pm

On Mon, Apr 8, 2019, 4:44 PM Brian Cain  wrote:

> Okay I will find something more centrally located.
>
> On Mon, Apr 8, 2019, 2:26 PM Francesco Petrogalli <
> francesco.petroga...@arm.com> wrote:
>
>> Hi Brian,
>>
>> 6 pm is a bit unfeasible for me, as I work on the other side of the city
>> (Southwest Parkway). How about meeting downtown, which hopefully is somehow
>> halfway for everybody, at least on average?
>>
>> Francesco
>>
>> > On Apr 7, 2019, at 3:04 PM, Brian Cain  wrote:
>> >
>> > Thursday 11 April
>> > Meet you at 6:00pm at Pour House (west of 183).
>> >
>> > Pour House
>> > 11835 Jollyville Rd, Austin, TX 78759
>> > http://pourhousepintsandpies.com/
>> >
>> > --
>> > -Brian
>>
>>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] April LLVM Austin social is this Thursday!

[Brian Cain via lldb-dev]

Okay I will find something more centrally located.

On Mon, Apr 8, 2019, 2:26 PM Francesco Petrogalli <
francesco.petroga...@arm.com> wrote:

> Hi Brian,
>
> 6 pm is a bit unfeasible for me, as I work on the other side of the city
> (Southwest Parkway). How about meeting downtown, which hopefully is somehow
> halfway for everybody, at least on average?
>
> Francesco
>
> > On Apr 7, 2019, at 3:04 PM, Brian Cain  wrote:
> >
> > Thursday 11 April
> > Meet you at 6:00pm at Pour House (west of 183).
> >
> > Pour House
> > 11835 Jollyville Rd, Austin, TX 78759
> > http://pourhousepintsandpies.com/
> >
> > --
> > -Brian
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] April LLVM Austin social is this Thursday!

[Brian Cain via lldb-dev]

Thursday 11 April
Meet you at 6:00pm at Pour House (west of 183).

Pour House
11835 Jollyville Rd, Austin, TX 78759
http://pourhousepintsandpies.com/

-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Ubuntu 18.04 looks good:

4f26c25bb628196101e781f11d79bd7af392c113
clang+llvm-7.1.0-rc1-x86_64-linux-gnu-ubuntu-18.04.tar.xz


On Wed, Mar 27, 2019 at 4:27 PM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hi,
>
> I've just tagged 7.1.0-rc1.  Testers, please begin testing and reporting
> results.
>
> Thanks,
> Tom
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

I forgot Ubuntu 14.04 is still useful for some folks (including me), so
I've only just now built it and uploaded:

552ea458b70961b7922a4bbe9de1434688342dbf
clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz


On Wed, Mar 20, 2019 at 8:39 AM Brian Cain  wrote:

> Uploaded ubuntu and SLES tarballs:
>
> db0a5f7729507ddc4b161eff70cffcf5de052347
> clang+llvm-8.0.0-x86_64-linux-sles11.3.tar.xz
> 2be69be355b012ae206dbc0ea7d84b831d77dc27
> clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz
> 6aeb8aa0998d37be67d886b878f27de5e5ccc5e4
> clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-18.04.tar.xz
>
>
> On Mon, Mar 18, 2019 at 8:04 AM Hans Wennborg via Release-testers <
> release-test...@lists.llvm.org> wrote:
>
>> Dear testers,
>>
>> 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.
>>
>> Apologies for being behind schedule. It took longer than planned this
>> time.
>>
>> Please build the final binaries and upload to the sftp.
>>
>> For those following along: this means 8.0.0 is done, but it will take
>> a few days to get all the tarballs ready and published on the release
>> web page. I will send the announcement once everything is ready.
>>
>> Thanks again everyone for your help with testing the release!
>>
>> Hans
>> ___
>> Release-testers mailing list
>> release-test...@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>>
>
>
> --
> -Brian
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy

[Brian Cain via lldb-dev]

On Tue, Mar 19, 2019 at 2:00 PM Tom Stellard via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> Hi,
>
> I would like to follow up on the previous thread[1], where there was a
> consensus
> to disallow merge commits in the llvm github repository, and start a
> discussion
> about how we should enforce this policy.
>
> Unfortunately, GitHub does not provide a convenient way to fully enforce
> this policy.
> We can enforce it for pull requests, but not for direct pushes to the
> master branch,
> so we will have to come up with our own solution if we want to completely
> prevent
> merge commits.  I've spent some time looking into this and here are a few
> options that I've come up with (If you are a GitHub expert and have other
> suggestions, please let us know):
>
> 1. Have either a status check or use the "Rebase and Merge" policy for
> pull requests
> to disallow merge commits.  Disable direct pushes to the master branch and
> update the
> git-llvm script to create a pull request when a developer does `git llvm
> push` and
> then have it automatically merged if there are no merge commits.
>
> 2. Enforce no merge commits for pull requests, but sill allow developers
> to push directly
> to master without checking for merge requests.  This is essentially a best
> effort
> approach where we avoid having to implement our own custom work-flow for
> committing,
> while accepting the possibility that someone might accidentally push a
> merge commit.
>
> 3. Disable direct pushes to master, don't update the git-llvm script and
> require all
> developers to use pull requests, where this policy will be enforced.
>
> Which option do you prefer?
>
>
>
I don't think I have a preference regarding merge commits but having a
status check where some subset of build + test takes place is a really good
idea, IMO.  It would be great if it were applied for everyone but if that
causes too many problems, I would settle for opt-in.  Preferably not
all-or-nothing on the check.

Regarding the scope of the check (boldly assuming one would be in place):
the more, the better (so long as it's stable and tolerable to the team).
Some dev teams that use GH have a bot that optimistically batch
builds-and-tests commits and when failures inevitably happen, contributors
are encouraged to triage and re-enqueue their PR for being built if they
can surmise the failure is not due to their change.

When contributing changes upstream, it takes away some of the
stress/challenge if you have some independent automaton verify that your
change doesn't cause regressions.  As it stands I feel like I should be on
standby for 24 to 72 hours after the commit in order to investigate/revert
if my change causes someone problems.  I realize that it's prudent to limit
the scope such that the checks don't create an enormous backlog.


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded ubuntu and SLES tarballs:

db0a5f7729507ddc4b161eff70cffcf5de052347
clang+llvm-8.0.0-x86_64-linux-sles11.3.tar.xz
2be69be355b012ae206dbc0ea7d84b831d77dc27
clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz
6aeb8aa0998d37be67d886b878f27de5e5ccc5e4
clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-18.04.tar.xz


On Mon, Mar 18, 2019 at 8:04 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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.
>
> Apologies for being behind schedule. It took longer than planned this time.
>
> Please build the final binaries and upload to the sftp.
>
> For those following along: this means 8.0.0 is done, but it will take
> a few days to get all the tarballs ready and published on the release
> web page. I will send the announcement once everything is ready.
>
> Thanks again everyone for your help with testing the release!
>
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Hans,

Sorry for the delay -- uploaded rc5 binaries:

d52493c1c1082ae6be0a322a1b2d4a81e9f0d6c7
clang+llvm-8.0.0-rc5-x86_64-linux-gnu-ubuntu-18.04.tar.xz
af43eb9c4394175d26ff795d35dea2a5b4db80fa
clang+llvm-8.0.0-rc5-x86_64-linux-gnu-ubuntu-14.04.tar.xz
635cb99931ac9b166fa60702ac05b8e3a09a0290
clang+llvm-8.0.0-rc5-x86_64-linux-sles11.3.tar.xz



On Tue, Mar 12, 2019 at 6:17 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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.
>
> As usual, please run the test script, share your results, and upload
> binaries.
>
> I'll publish source tarballs and docs as soon as possible, and binaries as
> they become available.
>
> Thanks for all your help so far, we're almost there :-)
>
> Cheers,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded SLES11, Ubuntu 14.04, 18.04 binaries.

9e59c0c667cd67c61600470d2e3107576b4707c8
clang+llvm-8.0.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz
0fd5690c11f045ae4d356619620778b0c17942ff
clang+llvm-8.0.0-rc3-x86_64-linux-gnu-ubuntu-18.04.tar.xz
6d1dc9b31d4f4d815b7cd18c8446404dc2a80a69
clang+llvm-8.0.0-rc3-x86_64-linux-sles11.3.tar.xz




On Wed, Feb 27, 2019 at 12:51 PM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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.
>
> Please take a close look at this release candidate. Unless anything
> bad comes up, this is probably very similar to what the final release
> will look like.
>
> Testers, please run the test script, share your results, and upload
> binaries.
>
> I'll publish source tarballs and docs as soon as possible, and
> binaries as they become available.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Any tips or suggestions on how to isolate or identify this defect?  It
seems non-trivial to bisect this failure.

Hans: presumably this bug should block the 8.0 release?

On Mon, Feb 11, 2019 at 8:37 AM Brian Cain  wrote:

> 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
> ---
> >
> Phase3/Release/llvmCore-8.0.0-rc2.obj/lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86ISelLowering.cpp.o:
>file format elf64-x86-64
> 121757c121757
> <  863: 48 8b 84 24 e0 05 00mov0x5e0(%rsp),%rax
> ---
> >  863: 48 8b 84 24 b0 01 00mov0x1b0(%rsp),%rax
> 121759c121759
> <  86b: 48 33 84 24 b0 01 00xor0x1b0(%rsp),%rax
> ---
> >  86b: 48 33 84 24 e0 05 00xor0x5e0(%rsp),%rax
> 121761,121762c121761,121762
> <  873: 8b 8c 24 e8 05 00 00mov0x5e8(%rsp),%ecx
> <  87a: 33 8c 24 b8 01 00 00xor0x1b8(%rsp),%ecx
> ---
> >  873: 8b 8c 24 b8 01 00 00mov0x1b8(%rsp),%ecx
> >  87a: 33 8c 24 e8 05 00 00xor0x5e8(%rsp),%ecx
>
>
> On Sat, Feb 9, 2019 at 9:54 AM Brian Cain  wrote:
>
>> rc2 build on Ubuntu 16.04 saw a stage 2/3 mismatch on
>> X86IselLowering.cpp.o -- I didn't try to build rc1 for 16.04 but I can try
>> it now to see if it's there too.
>>
>> I can pass along logs if anyone wants to investigate.
>>
>> On Thu, Feb 7, 2019 at 9:41 AM Hans Wennborg via Release-testers <
>> release-test...@lists.llvm.org> wrote:
>>
>>> Dear testers,
>>>
>>> 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.
>>>
>>> I'll get the source tarballs and docs published as soon as possible,
>>> and binaries as they become available.
>>>
>>> Thanks,
>>> Hans
>>> ___
>>> Release-testers mailing list
>>> release-test...@lists.llvm.org
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>>>
>>
>>
>>
>
> --
> -Brian
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

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
---
>
Phase3/Release/llvmCore-8.0.0-rc2.obj/lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86ISelLowering.cpp.o:
   file format elf64-x86-64
121757c121757
<  863: 48 8b 84 24 e0 05 00mov0x5e0(%rsp),%rax
---
>  863: 48 8b 84 24 b0 01 00mov0x1b0(%rsp),%rax
121759c121759
<  86b: 48 33 84 24 b0 01 00xor0x1b0(%rsp),%rax
---
>  86b: 48 33 84 24 e0 05 00xor0x5e0(%rsp),%rax
121761,121762c121761,121762
<  873: 8b 8c 24 e8 05 00 00mov0x5e8(%rsp),%ecx
<  87a: 33 8c 24 b8 01 00 00xor0x1b8(%rsp),%ecx
---
>  873: 8b 8c 24 b8 01 00 00mov0x1b8(%rsp),%ecx
>  87a: 33 8c 24 e8 05 00 00xor0x5e8(%rsp),%ecx


On Sat, Feb 9, 2019 at 9:54 AM Brian Cain  wrote:

> rc2 build on Ubuntu 16.04 saw a stage 2/3 mismatch on
> X86IselLowering.cpp.o -- I didn't try to build rc1 for 16.04 but I can try
> it now to see if it's there too.
>
> I can pass along logs if anyone wants to investigate.
>
> On Thu, Feb 7, 2019 at 9:41 AM Hans Wennborg via Release-testers <
> release-test...@lists.llvm.org> wrote:
>
>> Dear testers,
>>
>> 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.
>>
>> I'll get the source tarballs and docs published as soon as possible,
>> and binaries as they become available.
>>
>> Thanks,
>> Hans
>> ___
>> Release-testers mailing list
>> release-test...@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>>
>
>
>

-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

rc2 build on Ubuntu 16.04 saw a stage 2/3 mismatch on X86IselLowering.cpp.o
-- I didn't try to build rc1 for 16.04 but I can try it now to see if it's
there too.

I can pass along logs if anyone wants to investigate.

On Thu, Feb 7, 2019 at 9:41 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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.
>
> I'll get the source tarballs and docs published as soon as possible,
> and binaries as they become available.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

On Tue, Jan 8, 2019 at 11:25 PM Tom Stellard  wrote:

> 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, releases.llvm.org only shows Windows and FreeBSD tarballs for 7.0.1
from what I can see.

Also, the front page of https://releases.llvm.org/ needs a new entry for
7.0.1 in the table under "Download".


>
> > On Mon, Dec 24, 2018 at 7:38 AM Brian Cain via cfe-dev <
> cfe-...@lists.llvm.org > wrote:
> >
> > 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
> clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-14.04.tar.xz
> > 5e2b33ac129b8471683dccaeb2818004eb5acea8
> clang+llvm-7.0.1-x86_64-linux-sles11.3.tar.xz
> >
> >
> > On Thu, Dec 20, 2018 at 12:18 PM Dimitry Andric via Release-testers <
> release-test...@lists.llvm.org >
> wrote:
> >
> > On 20 Dec 2018, at 01:23, Tom Stellard via Release-testers <
> release-test...@lists.llvm.org >
> 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(7.0.1 rc3: 52444)
> > Passes With Retry  :   n/a(7.0.1 rc3: 1)
> > Expected Failures  :   232(7.0.1 rc3:   232)
> > Unsupported Tests  :  3687(7.0.1 rc3:  3687)
> > Unexpected Passes  : 1(7.0.1 rc3: 1)
> > Unexpected Failures:   491(7.0.1 rc3:   491)
> >
> > Test-suite results on amd64-freebsd11 did not change:
> >
> > Expected Passes:   903(7.0.1 rc3:   903)
> > Unexpected Failures: 3(7.0.1 rc3: 3)
> >
> > Test results on i386-freebsd11 had 1 more Expected Pass compared
> to 7.0.1 rc3, and 3 less Unexpected Failures:
> >
> > Expected Passes: 50254(7.0.1 rc3: 50253)
> > Passes With Retry  : 2(7.0.1 rc3:   n/a)
> > Expected Failures  :   226(7.0.1 rc3:   226)
> > Unsupported Tests  :  2502(7.0.1 rc3:  2502)
> > Unexpected Failures:   272(7.0.1 rc3:   275)
> >
> > The test-suite still doesn't build on i386-freebsd11, but that
> is a known issue.
> >
> > I have uploaded:
> >
> > SHA256 (clang+llvm-7.0.1-amd64-unknown-freebsd11.tar.xz) =
> 617be68f00c7a80fb77ee5a124b800aadab64dff052acf51428da3af3f58e407
> > SHA256 (clang+llvm-7.0.1-i386-unknown-freebsd11.tar.xz) =
> 1f696728db8cd4850e0d97ea6bb9d8f3a715fa05fec04ff5618a3f2da6ae7d36
> >
> > -Dimitry
> >
> > ___
> > Release-testers mailing list
> > release-test...@lists.llvm.org  release-test...@lists.llvm.org>
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
> >
> >
> >
> > --
> > -Brian
> > ___
> > cfe-dev mailing list
> > cfe-...@lists.llvm.org 
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
> >
> >
> >
> > ___
> > Release-testers mailing list
> > release-test...@lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
> >
>
>

-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

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
clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-14.04.tar.xz
5e2b33ac129b8471683dccaeb2818004eb5acea8
clang+llvm-7.0.1-x86_64-linux-sles11.3.tar.xz


On Thu, Dec 20, 2018 at 12:18 PM Dimitry Andric via Release-testers <
release-test...@lists.llvm.org> wrote:

> On 20 Dec 2018, at 01:23, Tom Stellard via Release-testers <
> release-test...@lists.llvm.org> 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(7.0.1 rc3: 52444)
> Passes With Retry  :   n/a(7.0.1 rc3: 1)
> Expected Failures  :   232(7.0.1 rc3:   232)
> Unsupported Tests  :  3687(7.0.1 rc3:  3687)
> Unexpected Passes  : 1(7.0.1 rc3: 1)
> Unexpected Failures:   491(7.0.1 rc3:   491)
>
> Test-suite results on amd64-freebsd11 did not change:
>
> Expected Passes:   903(7.0.1 rc3:   903)
> Unexpected Failures: 3(7.0.1 rc3: 3)
>
> Test results on i386-freebsd11 had 1 more Expected Pass compared to 7.0.1
> rc3, and 3 less Unexpected Failures:
>
> Expected Passes: 50254(7.0.1 rc3: 50253)
> Passes With Retry  : 2(7.0.1 rc3:   n/a)
> Expected Failures  :   226(7.0.1 rc3:   226)
> Unsupported Tests  :  2502(7.0.1 rc3:  2502)
> Unexpected Failures:   272(7.0.1 rc3:   275)
>
> The test-suite still doesn't build on i386-freebsd11, but that is a known
> issue.
>
> I have uploaded:
>
> SHA256 (clang+llvm-7.0.1-amd64-unknown-freebsd11.tar.xz) =
> 617be68f00c7a80fb77ee5a124b800aadab64dff052acf51428da3af3f58e407
> SHA256 (clang+llvm-7.0.1-i386-unknown-freebsd11.tar.xz) =
> 1f696728db8cd4850e0d97ea6bb9d8f3a715fa05fec04ff5618a3f2da6ae7d36
>
> -Dimitry
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

SLES binary uploaded:

181e1729263dcb1abc650311c4d42dbef13ae805
clang+llvm-7.0.1-rc2-x86_64-linux-sles11.3.tar.xz

... I will try to get to ubuntu this week.

On Fri, Nov 2, 2018 at 9:36 PM Tom Stellard via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> Hi,
>
> 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.
>
> Remember, you can continue to submit merge requests up until Nov, 21,
> so keep testing and submitting fixes.
>
> Thanks,
> Tom
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded SLES binaries:

07d289c409e359f1d453d3b3ff66dfa36889d28b
clang+llvm-7.0.0-x86_64-linux-sles11.3.tar.xz
2c07e6f7ebcb71852ad3fe8d69dc7ca3ee580a59
clang+llvm-7.0.0-x86_64-linux-sles12.3.tar.xz


On Mon, Sep 17, 2018 at 6:42 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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.
>
> Please build the final binaries and upload to the sftp.
>
> For those following along: this means 7.0.0 is done, but it will take
> a few days to get all the tarballs ready and published on the web
> page. I will send the announcement once everything is ready.
>
> Thanks again everyone for your work!
>
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded sles binaries.

ba4e93b281bc53372cea22da624c02dad566a7b6
clang+llvm-7.0.0-rc3-x86_64-linux-sles11.3.tar.xz
d3cbc4a96adbfd5480601bd6a9faf62879976cf8
clang+llvm-7.0.0-rc3-x86_64-linux-sles12.3.tar.xz


On Mon, Sep 10, 2018 at 9:13 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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 release will look like.
>
> Please run the test script, share your results and upload binaries.
>
> Please also take a look at the release notes and other docs; small
> changes to those are still welcome.
>
> The sources and docs will show up at
> https://prereleases.llvm.org/7.0.0/#rc3 anytime now, and binaries will
> be posted when they're ready.
>
> Thanks everyone for your work on this release!
>
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

SLES11 rc1 build failed, opened PR38589.

Uploaded SLES12 rc1:
39ba1263db364999357fae8c6f2829b8fce7cfdd
clang+llvm-7.0.0-rc1-x86_64-linux-sles12.3.tar.xz



On Fri, Aug 3, 2018 at 6:38 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> 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 script, share the results, and upload binaries.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Ok, yes, you're right -- thanks for clarification.

On Mon, Mar 5, 2018 at 10:37 AM, Jonas Hahnfeld  wrote:

> libc++.so should be a linker script that automatically pulls in libc++abi
> (see "Failed to read file header" in your output). And IIRC libc++abi is
> only one possible implementation that may be used by libc++, but I'm no
> expert here...
>
>
> Am 2018-03-05 17:33, schrieb Brian Cain:
>
>> Isn't libc++.so dependent on libc++abi.so?
>>
>> On Mon, Mar 5, 2018 at 10:30 AM, Jonas Hahnfeld 
>> wrote:
>>
>> From what I can see all of the libraries without RPATH are runtime
>>> libraries that are used by binaries compiled with Clang. I think
>>> they don't have a dependency on other libraries in that directory,
>>> so what would be the advantage of having RPATH set on them?
>>>
>>> Regards,
>>> Jonas
>>>
>>> Am 2018-03-05 17:23, schrieb Brian Cain via llvm-dev:
>>>
>>> It was just brought to my attention that the RPATH configuration
>>> isn't
>>> uniform among the libraries produced by the release.  Some use
>>> $ORIGIN../lib/ and others have none.  Is this by design?  It seems
>>> like it might be ideal for all of them to be configured the same
>>> way.
>>> If that makes sense I'll create a corresponding feature request.
>>>
>>> $ for f in
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/lib*.so*; do
>>> echo
>>> $f; readelf -d $f|grep RUNPATH; done
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1
>>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1.0
>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so.6
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so.6.0
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so
>>> readelf: Error:
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so:
>>> Failed
>>> to read file header
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so.1
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so.1.0
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libgomp.so
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libiomp5.so
>>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb
>> IntelFeatures.so
>>
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb
>> IntelFeatures.so.6
>>
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb
>> IntelFeatures.so.6.0.0
>>
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so.6
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so.6.0.0
>>
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so.6
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so.6.0.0
>>> 0x001d (RUNPATH)Library runpath:
>>> [$ORIGIN/../lib]
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libomp.so
>>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libompt
>> arget.rtl.x86_64.so
>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libomptarget.so
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so.1
>>>
>>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so.1.0
>>
>>>
>>> On Sun, Mar 4, 2018 at 10:54 AM, Brian Cain 
>>> wrote:
>>>
>>> Uploaded ubuntu, SLES11, SLES12 binaries.
>>>
>>> 4907dbd37f4e5265a2f1252d9d7b5e5b0a9c0ec1
>>> clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz
>>> 360b26fcd9eafe5ca9c4baa89c38339bc587c094
>>> clang+llvm-6.0.0-x86_64-linux-sles11.3.tar.xz
>>> ce525cf949ef86409bc3f4f492035225989eecfd
>>> clang+llvm-6.0.0-x86_64-linux-sles12.2.tar.xz
>>>
>>> On Fri, Mar 2, 2018 at 6:17 AM, Hans Wennborg via Release-testers
>>> 

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

[Brian Cain via lldb-dev]

Isn't libc++.so dependent on libc++abi.so?

On Mon, Mar 5, 2018 at 10:30 AM, Jonas Hahnfeld  wrote:

> From what I can see all of the libraries without RPATH are runtime
> libraries that are used by binaries compiled with Clang. I think they don't
> have a dependency on other libraries in that directory, so what would be
> the advantage of having RPATH set on them?
>
> Regards,
> Jonas
>
>
> Am 2018-03-05 17:23, schrieb Brian Cain via llvm-dev:
>
>> It was just brought to my attention that the RPATH configuration isn't
>> uniform among the libraries produced by the release.  Some use
>> $ORIGIN../lib/ and others have none.  Is this by design?  It seems
>> like it might be ideal for all of them to be configured the same way.
>> If that makes sense I'll create a corresponding feature request.
>>
>> $ for f in
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/lib*.so*; do echo
>> $f; readelf -d $f|grep RUNPATH; done
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1.0
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so.6
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so.6.0
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so
>> readelf: Error:
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so: Failed
>> to read file header
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so.1
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so.1.0
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libgomp.so
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libiomp5.so
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb
>> IntelFeatures.so
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb
>> IntelFeatures.so.6
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb
>> IntelFeatures.so.6.0.0
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so.6
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so.6.0.0
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so.6
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so.6.0.0
>>  0x001d (RUNPATH)Library runpath:
>> [$ORIGIN/../lib]
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libomp.so
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libompt
>> arget.rtl.x86_64.so
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libomptarget.so
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so.1
>> ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so.1.0
>>
>> On Sun, Mar 4, 2018 at 10:54 AM, Brian Cain 
>> wrote:
>>
>> Uploaded ubuntu, SLES11, SLES12 binaries.
>>>
>>> 4907dbd37f4e5265a2f1252d9d7b5e5b0a9c0ec1
>>> clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz
>>> 360b26fcd9eafe5ca9c4baa89c38339bc587c094
>>> clang+llvm-6.0.0-x86_64-linux-sles11.3.tar.xz
>>> ce525cf949ef86409bc3f4f492035225989eecfd
>>> clang+llvm-6.0.0-x86_64-linux-sles12.2.tar.xz
>>>
>>> On Fri, Mar 2, 2018 at 6:17 AM, Hans Wennborg via Release-testers
>>>  wrote:
>>>
>>> Dear testers,

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

 For those following along: this means llvm-6.0.0 is complete, but
 it
 will take a few days to get all the tarballs ready and published
 on
 the web page. I will send the announcement once everything is
 ready.

 

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

[Brian Cain via lldb-dev]

It was just brought to my attention that the RPATH configuration isn't
uniform among the libraries produced by the release.  Some use
$ORIGIN../lib/ and others have none.  Is this by design?  It seems like it
might be ideal for all of them to be configured the same way.  If that
makes sense I'll create a corresponding feature request.

$ for f in ./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/lib*.so*;
do echo $f; readelf -d $f|grep RUNPATH; done
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1.0
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so.6
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libclang.so.6.0
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so
readelf: Error:
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so: Failed to
read file header
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so.1
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++.so.1.0
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libgomp.so
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libiomp5.so
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldbIntelFeatures.so
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldbIntelFeatures.so.6
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldbIntelFeatures.so.6.0.0
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so.6
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/liblldb.so.6.0.0
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so.6
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libLTO.so.6.0.0
 0x001d (RUNPATH)Library runpath: [$ORIGIN/../lib]
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libomp.so
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/
libomptarget.rtl.x86_64.so
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libomptarget.so
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so.1
./clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04/lib/libunwind.so.1.0


On Sun, Mar 4, 2018 at 10:54 AM, Brian Cain  wrote:

>
> Uploaded ubuntu, SLES11, SLES12 binaries.
>
> 4907dbd37f4e5265a2f1252d9d7b5e5b0a9c0ec1  clang+llvm-6.0.0-x86_64-linux-
> gnu-ubuntu-14.04.tar.xz
> 360b26fcd9eafe5ca9c4baa89c38339bc587c094  clang+llvm-6.0.0-x86_64-linux-
> sles11.3.tar.xz
> ce525cf949ef86409bc3f4f492035225989eecfd  clang+llvm-6.0.0-x86_64-linux-
> sles12.2.tar.xz
>
>
> On Fri, Mar 2, 2018 at 6:17 AM, Hans Wennborg via Release-testers <
> release-test...@lists.llvm.org> wrote:
>
>> Dear testers,
>>
>> 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 sftp.
>>
>> For those following along: this means llvm-6.0.0 is complete, but it
>> will take a few days to get all the tarballs ready and published on
>> the web page. I will send the announcement once everything is ready.
>>
>> Many thanks to everyone for your hard work!
>>
>> Hans
>> ___
>> Release-testers mailing list
>> release-test...@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>>
>
>
>
> --
> -Brian
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded ubuntu, SLES11, SLES12 binaries.

4907dbd37f4e5265a2f1252d9d7b5e5b0a9c0ec1
clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz
360b26fcd9eafe5ca9c4baa89c38339bc587c094
clang+llvm-6.0.0-x86_64-linux-sles11.3.tar.xz
ce525cf949ef86409bc3f4f492035225989eecfd
clang+llvm-6.0.0-x86_64-linux-sles12.2.tar.xz


On Fri, Mar 2, 2018 at 6:17 AM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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 sftp.
>
> For those following along: this means llvm-6.0.0 is complete, but it
> will take a few days to get all the tarballs ready and published on
> the web page. I will send the announcement once everything is ready.
>
> Many thanks to everyone for your hard work!
>
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

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-test...@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 we'll actually
> end up blocking on all of them. So depending on what comes up, this
> release candidate is probably pretty close to what the final release
> will look like (I'm still hoping for more release notes, though).
>
> I'm hoping we can get to 'final' sometime next week.
>
> Please test, let me know how it goes, and upload binaries.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded

afeb7f66eedd4d576ba8df9b4a551bb1908186e6
clang+llvm-6.0.0-rc1-linux-x86_64-sles11.3.tar.xz


On Wed, Jan 17, 2018 at 11:53 AM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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 upload binaries.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

On Tue, Sep 5, 2017 at 1:24 PM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> The final version of 5.0.0 has just been tagged. There were no changes
> after rc5.
>
> Please build the final binaries and upload to the sftp.
>
> For those following along: this means 5.0.0 is complete, but it will
> take a few days to get the tarballs ready and published on the web
> page. I will send the announcement once everything's ready.
>
>
Hans,

Sorry it's a little late -- I got a request for ubuntu x86_64.

Uploaded clang+llvm-5.0.0-linux-x86_64-ubuntu16.04.tar.xz and
clang+llvm-5.0.0-linux-x86_64-ubuntu14.04.tar.xz

9cb81c92aa4d3f9707a9b8413c4d24b8dee90c59  clang+llvm-5.0.0-linux-x86_
64-ubuntu16.04.tar.xz
eee510a7399040636db2c4199beda7c735314938  clang+llvm-5.0.0-linux-x86_
64-ubuntu14.04.tar.xz


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded SLES11 binary, no new failures.  Test-suite no longer encounters
SIGILL (PR34168) -- addressed by r312334, thanks!

c09be7925c7eca370ea924d3b1da5e5ebf55146c
 clang+llvm-5.0.0-rc5-linux-x86_64-sles11.3.tar.xz


On Fri, Sep 1, 2017 at 4:07 PM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hello again,
>
> 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.
>
> Please do a quick test; if there are no new issues, this will become
> 'final' early next week.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded rc4 and rc3 for SLES11.  No new issues.

5560fd8bf543bf3cdcaf55caef159664bd2749f3  clang+llvm-5.0.0-rc3-linux-
x86_64-sles11.3.tar.xz
effbb3a69efec75a67566d91dd4a9e685c2df15d  clang+llvm-5.0.0-rc4-linux-
x86_64-sles11.3.tar.xz


On Tue, Aug 29, 2017 at 6:52 PM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Hello testers,
>
> 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.
>
> Please test and let me know if there are any issues.
>
> Cheers,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Opened https://bugs.llvm.org/show_bug.cgi?id=34168

rc2 uploaded
to /home/testers/uploads/clang+llvm-5.0.0-rc2-linux-x86_64-sles11.3.tar.xz
-- I tried to use /data/testers-uploads/ but that failed.

292e39fe52d7404fcd5cd962cf8917600d45f507
 rc2/clang+llvm-5.0.0-rc2-linux-x86_64-sles11.3.tar.xz


On Fri, Aug 11, 2017 at 7:36 PM, Matthias Braun  wrote:

> +CC Alina
>
> Maybe the bitcode is generated too aggressively and we should find ways to
> disable the Bitcode tests if the host CPU isn't new enough (or
> alternatively disable the bitcode tests by default and only enable them
> when someone asks for them via TEST_SUITE_SUBDIRS?)
>
> - Matthias
>
> > On Aug 11, 2017, at 4:44 PM, Hans Wennborg via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
> >
> > I'm not aware of a bug filed for this, so please file one. I don't
> > know much about the workings of test-suite myself, though.
> >
> > On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain 
> wrote:
> >> Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem
> to be
> >> failing for me with SIGILL.  I'm guessing that my host CPU doesn't
> support
> >> the instructions we're testing?
> >>
> >> Is there already a bug on this failure?  Are there any CPUID-style
> feature
> >> detection flags I can easily add to mark these tests UNSUPPORTED for, or
> >> would I have to write this detection feature?
> >>
> >> On Thu, Aug 10, 2017 at 9:00 PM, Hans Wennborg via Release-testers
> >>  wrote:
> >>>
> >>> Dear testers,
> >>>
> >>> 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.
> >>>
> >>> Please build, test and upload binaries to the sftp. When uploading,
> >>> make sure to use the /data/testers-uploads/ directory on the server.
> >>> Let me know if there are any issues.
> >>>
> >>> I'll upload sources, docs and your binaries to the pre-release website
> >>> once they're ready.
> >>>
> >>> Cheers,
> >>> Hans
> >>> ___
> >>> Release-testers mailing list
> >>> release-test...@lists.llvm.org
> >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
> >>
> >>
> >>
> >>
> >> --
> >> -Brian
> > ___
> > LLVM Developers mailing list
> > llvm-...@lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem to be
failing for me with SIGILL.  I'm guessing that my host CPU doesn't support
the instructions we're testing?

Is there already a bug on this failure?  Are there any CPUID-style feature
detection flags I can easily add to mark these tests UNSUPPORTED for, or
would I have to write this detection feature?

On Thu, Aug 10, 2017 at 9:00 PM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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.
>
> Please build, test and upload binaries to the sftp. When uploading,
> make sure to use the /data/testers-uploads/ directory on the server.
> Let me know if there are any issues.
>
> I'll upload sources, docs and your binaries to the pre-release website
> once they're ready.
>
> Cheers,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

[earlier I had accidentally sent this message to only Hans, re-sending as
reply-all now]

When I tried rc1 on sles11.3 x86_64, msan's getrlimit test fails to build
for lack of prlimit().  SLES11.3 has glibc 2.11.3.  Is there a minimum
required glibc?  I think this test implementation previously used
getrlimit(), which is present on glibc2.11.3.



On Fri, Jul 29, 2016 at 5:57 PM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 3.9.0-rc1 was just tagged from the 3.9 branch at r277207.
>
> This took a little longer than I'd hoped, but I think the branch is in
> a decent state now.
>
> There are still open merge requests and bugs, but I'd like to get the
> real testing started to see where we're at.
>
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the
> pre-release page once they're ready.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [llvm-dev] GitHub anyone?

[Brian Cain via lldb-dev]

On Thu, Jun 2, 2016 at 11:21 AM, Tanya Lattner via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> I personally find this email thread very hard to follow and read (this
> isn’t anyones fault.. its just a lot of replies). I am sure others do as
> well. I think it would be good to have a form/survey of some sort that can
> get feedback from users such as: who they are, how they use
> LLVM/contributions/etc,  if they are pro-github move, how it impacts them,
> etc. People could then submit their feedback in an organized way and we
> could get a better idea of how the community feels on the topic.
>

While I sympathize, I wonder if a survey is appropriate.  It gives equal
weight to all voices but not all voices are equally impacted by the
pros/cons.  I am in favor of a github/lab/etc transition but I've only
lurked on the list and built/tested a couple of releases for older
platforms.  I would think opinions of those who have lots of work with
commits/reviews/content should probably be weighed heavier than mine.
Perhaps the survey could ask for a voluntary high/medium/low activity level
for normalizing the votes?

-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

CentOS 6 uploaded and tested.

05141a39af0998770e4bf1953980a10f69aca450
 clang+llvm-3.8.0-linux-x86_64-centos6.tar.xz


On Wed, Mar 2, 2016 at 6:33 PM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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.
>
> For others following along: yes, this means 3.8.0 is complete, but it
> takes a couple of days to get the source and binary tarballs built. I
> will send the release announcement when everything's ready.
>
> Many thanks for all your work!
> Hans
>
>  [1].
> http://lists.llvm.org/pipermail/llvm-branch-commits/2016-March/009883.html
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

On Wed, Mar 2, 2016 at 6:33 PM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 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.
>
> For others following along: yes, this means 3.8.0 is complete, but it
> takes a couple of days to get the source and binary tarballs built. I
> will send the release announcement when everything's ready.
>
>
>
Uploaded clang+llvm-3.8.0-x86_64-sles11.3-linux-gnu.tar.xz
and clang+llvm-3.8.0-linux-armhf-vivid.tar.xz

7388c9ec1c9680a3366dd40e0bb8acc655b3e3ec
 clang+llvm-3.8.0-linux-armhf-vivid.tar.xz
c33ab986d5b8dce7af88ca1b748240f98c4ed2c5
 clang+llvm-3.8.0-x86_64-sles11.3-linux-gnu.tar.xz




-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Uploaded clang+llvm-3.8.0-rc3-linux-x86_64-sles11.3.tar.xz
and clang+llvm-3.8.0-rc3-linux-armhf-vivid.tar.xz

f8f8b0ff8f9709cbf63097727a96fde5054efefe
 rc3/clang+llvm-3.8.0-rc3-linux-x86_64-sles11.3.tar.xz
9202d52a9bff5464d0b76750c41ffec0d7d99c17
 rc3/clang+llvm-3.8.0-rc3-linux-armhf-vivid.tar.xz

No new unexpected failures for each.

On Tue, Feb 23, 2016 at 3:51 PM, Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> Release Candidate 3 has just been tagged [1]. Please build, test, and
> upload to the sftp.
>
> If there are no regressions from previous release candidates, this
> will be the last release candidate before the final release.
>
> Release notes can still go into the branch.
>
> Thanks again for all your work!
> Hans
>
>  [1]
> http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

Tested RC2 w/SLES11.3, x86_64.  No regressions.

81c1ea3fafee883fbbd396779d1e62714304eff6
 rc2/clang+llvm-3.8.0-rc2-linux-x86_64-sles11.3.tar.xz


On Tue, Feb 2, 2016 at 3:15 PM, Hans Wennborg via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> Dear testers,
>
> 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 time for
> another round of RC testing.
>
> This RC comes a little behind schedule, sorry about that, but I'm
> still optimistic about hitting the target of releasing towards the end
> of February.
>
> Thanks for all the work you've put into this release so far!
>
> Hans
>
>  [1]
> http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009739.html
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

On Thu, Jan 21, 2016 at 9:52 PM, Brian Cain  wrote:

> On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier  wrote:
>
>>
>> On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev <
>> cfe-...@lists.llvm.org> wrote:
>>
>>> SuSE Linux Enterprise Server 11SP3 x86_64
>>>
>>> Looks like I see several failures that weren't in 3.7.1.  Is there any
>>> way to tell whether these are regressions vs new-to-3.8.0-but-failing?  The
>>> MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors were
>>> not in 3.7.1.
>>>
>>>
>> All of the libc++ failures seem like non-issues and should be in 3.7.1.
>> Did you change or upgrade your platform or libc version?  I'm not sure
>> about the libc++abi error though.
>>
>
> I don't recall any changes to libc.  Attached is the testing log from
> 3.7.1 rc2 (I don't have logs from -final handy).
>
> I can repeat a 3.7.1 release build on this system now.  I don't think the
> results will change, though.
>
>
I discussed this more with Eric off-list and I think we've come to the
conclusion that this was not a regression, it was my error.

It's a bit tricky -- what should I expect for a new platform?  All failing
tests are likely failing because they can't be/aren't yet supported?  It's
tough to distinguish -- are they real bugs to be fixed, errors in the
build/release process?
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

I built rc1 on Ubuntu 15.04 armhf.  Many tests fail (560, nearly all are
libc++ and libc++abi).  There's also a handful of unexpected passing tests
(12).

e29ac68df06f7fad8c773b7da9778469d84f3f32
 rc1/clang+llvm-3.8.0-rc1-linux-armhf-vivid.tar.xz


On Tue, Jan 19, 2016 at 5:47 PM, Hans Wennborg  wrote:

> Dear testers,
>
> Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at
> r258223. (It took a little longer than I'd planned, sorry about that.)
>
> There are still a bunch of open merge requests and bug reports, but I
> wanted to get the tag in so we can see what the build and test status
> are on the various platforms.
>
> I verified that it currently builds and tests cleanly for me on x86_64
> Linux, Mac OS X* and Windows.
>
> Please build, test, and upload binaries to the sftp. Let me know if how it
> goes.
>
> Thanks,
> Hans
>
>
> [*] For Mac, I had to set CFLAGS="-isysroot `xcrun -show-sdk-path`"
> CXXFLAGS="-isysroot `xcrun -show-sdk-path`" for the build to work,
> otherwise stage-2 Clang couldn't find the SDK. I don't remember if I
> had to do this last time; maybe some upgrade changed something.
>



-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[Brian Cain via lldb-dev]

I can do SLES.  I also have an arm7l ubuntu 15.x machine if no one else is
already covering that target.

On Mon, Dec 14, 2015 at 3:26 PM, Nikola Smiljanic 
wrote:

> I'll do Fedora and openSUSE.
>
> On Mon, Dec 14, 2015 at 9:08 PM, Daniel Sanders  > wrote:
>
>> Sounds good to me. I'll do the usual mips packages.
>>
>> > -Original Message-
>> > From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf
>> > Of Hans Wennborg
>> > Sent: 11 December 2015 23:15
>> > To: llvm-dev; cfe-dev; lldb-dev@lists.llvm.org;
>> openmp-...@lists.llvm.org
>> > Cc: Dimitry Andric; Sebastian Dreßler; Renato Golin; Pavel Labath;
>> Sylvestre
>> > Ledru; Ed Maste; Ben Pope; Daniel Sanders; Nikola Smiljanić; Brian
>> Cain; Tom
>> > Stellard
>> > Subject: [3.8 Release] Schedule and call for testers
>> >
>> > Dear everyone,
>> >
>> > 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 release, you're cc'd on this email.)
>> >
>> > I propose the following schedule for the 3.8 release:
>> >
>> > - 13 January: Create 3.8 branch. Testing Phase 1: RC1 binaries built
>> > and tested, bugs fixed. Any almost-complete features need to be
>> > wrapped up or disabled on the branch ASAP, and definitely before this
>> > phase ends.
>> >
>> > - 27 January: Testing Phase 2: RC2 binaries built and tested. Only
>> > critical bug fixes from now on. Further RCs published as we approach..
>> >
>> > - 18 February: Cut the final release, build binaries, ship when ready.
>> >
>> > Unless there are any objections, I'll post this on the web page.
>> >
>> > Cheers,
>> > Hans
>>
>
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev