llvm dev - Aug 2017 - [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

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

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-testers at 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-testers at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170811/fd88454c/attachment.html>

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 <brian.cain at gmail.com>
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
> <release-testers at 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-testers at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
>
>
>
> --
> -Brian

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

[  DEATH   ] ==5754==AddressSanitizer CHECK failed:
/home/dim/llvm-5.0.0/rc2/llvm.src/projects/compiler-rt/lib/asan/asan_errors.h:99
"((second_free_stack->size)) > ((0))" (0x0, 0x0)

or:

[  DEATH   ] ==7514==AddressSanitizer CHECK failed:
/home/dim/llvm-5.0.0/rc2/llvm.src/projects/compiler-rt/lib/asan/asan_descriptions.cc:176
"((id)) != (0)" (0x0, 0x0)

This is likely due to r305058, as mentioned in my report for rc1.

I could not upload my tarballs, since the upload disk appears to be full:

sftp> df -h
    Size     Used    Avail   (root)    %Capacity
   7.7GB    7.3GB    192KB    425MB          94%

So I have uploaded them to my own server, here:

http://www.andric.com/freebsd/clang/clang+llvm-5.0.0-rc2-amd64-unknown-freebsd10.tar.xz
http://www.andric.com/freebsd/clang/clang+llvm-5.0.0-rc2-i386-unknown-freebsd10.tar.xz

SHA256 (clang+llvm-5.0.0-rc2-amd64-unknown-freebsd10.tar.xz) =
8e27a2fe43785eff1927100c59bee3d662c3e75f28adf87cb8ce31253a5dd67f
SHA256 (clang+llvm-5.0.0-rc2-i386-unknown-freebsd10.tar.xz) =
421ccd60c22c751711fca0169f5c7461ef537a110e86c91d619e7d2f5b0452c5

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170814/df8d6100/attachment.sig>

On Thu, Aug 10, 2017 at 7:00 PM, Hans Wennborg <hans at chromium.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.
Windows is ready:

$ sha1sum *5.0.0-rc2*
7376bfd5d33fa4d4d8102d1469ad01f62686b8fb  LLVM-5.0.0-rc2-win32.exe
66b92d054ed36caf96e0a584a43816f3ad79b5f7  LLVM-5.0.0-rc2-win64.exe

All green in Debian:
https://buildd.debian.org/status/package.php?p=llvm-toolchain-5.0

Except that I had to force the usage of gcc 6 instead gcc 7 because of

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

(other versions are also affected)

S


Le 11/08/2017 à 04:00, Hans Wennborg via Release-testers a
écrit :
> 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-testers at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170815/7a59724e/attachment.html>

W dniu czw, 10.08.2017 o godzinie 19∶00 -0700, użytkownik Hans Wennborg
via cfe-dev napisał:
> 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'm sorry for not replying earlier but I have much less time than I wish
I'd have. Nevertheless, I'm trying to regularly test the release_50
branch and fix the regressions Gentoo is seeing.

It seems that we've been able to fix most of the apparent issues.
The two things that still remain are:

a. lldb fails to build with (more) linking errors -- there are already
two related fixes in the trunk, and I'm currently working on a third one
and should have a complete set of patches to backport on the weekend,

b. all DFSan tests segfault for me -- I have tried to bisect it, and it
seems that all old versions started failing just the same all
of a sudden. I suspect this might be related to system upgrade but
haven't been able to find time to properly investigate. Hopefully I'd be
able to at least provide more data soon.

Thanks for all the hard work.

-- 
Best regards,
Michał Górny

Hi,

There are no regressions from RC1 on Darwin.

I've uploaded clang+llvm-5.0.0-rc2-x86_64-apple-darwin.tar.xz to
/data/testers-uploads.

SHA 1: 8ffaf7ab44e7e7fe582dc9573aad9745ee63e186
SHA 256: 578c18ceb6485fd2fcac329a7a5fe7e55d1c70669a942651d49cdc3ea626a5af

I've also resurrected the Darwin bot which tests the release branch (thanks
to Mehdi for creating the original!):

 
http://lab.llvm.org:8080/green/view/All/job/clang-stage1-configure-RA-release-5/

thanks,
vedant
> On Aug 10, 2017, at 7:00 PM, Hans Wennborg via llvm-dev <llvm-dev at
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
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

On Thu, Aug 17, 2017 at 4:03 PM, Vedant Kumar <vsk at apple.com>
wrote:
> Hi,
>
> There are no regressions from RC1 on Darwin.
>
> I've uploaded clang+llvm-5.0.0-rc2-x86_64-apple-darwin.tar.xz to
/data/testers-uploads.
>
> SHA 1: 8ffaf7ab44e7e7fe582dc9573aad9745ee63e186
> SHA 256: 578c18ceb6485fd2fcac329a7a5fe7e55d1c70669a942651d49cdc3ea626a5af
Thanks! I've added them to the pre-release page.
>
> I've also resurrected the Darwin bot which tests the release branch
(thanks to Mehdi for creating the original!):
>
>  
http://lab.llvm.org:8080/green/view/All/job/clang-stage1-configure-RA-release-5/
That's awesome! Many thanks.

On Mon, Aug 14, 2017 at 3:36 AM, Dimitry Andric <dimitry at andric.com>
wrote:
> On 11 Aug 2017, at 04:00, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:
>> 5.0.0-rc2 was just tagged.
>>
>> I know we still have a bunch of open release blockers, but there has
>> been a lot of merged patches and I'd like to find out what the
status
>> is.
>
> As in the last rc, most of the ASan tests failed with either:
>
> [  DEATH   ] ==5754==AddressSanitizer CHECK failed:
/home/dim/llvm-5.0.0/rc2/llvm.src/projects/compiler-rt/lib/asan/asan_errors.h:99
"((second_free_stack->size)) > ((0))" (0x0, 0x0)
>
> or:
>
> [  DEATH   ] ==7514==AddressSanitizer CHECK failed:
/home/dim/llvm-5.0.0/rc2/llvm.src/projects/compiler-rt/lib/asan/asan_descriptions.cc:176
"((id)) != (0)" (0x0, 0x0)
>
> This is likely due to r305058, as mentioned in my report for rc1.
Was there ever any progress on this, or at least a bug report filed?
Do you think it's just the tests that are failing, or does it mean
ASan is broken on FreeBSD? How severe is this issue from your
perspective?

Thanks,
Hans