Hans Wennborg via llvm-dev
2018-Feb-07 20:51 UTC
[llvm-dev] [6.0.0 Release] Release Candidate 2 tagged
Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans
Andrew Kelley via llvm-dev
2018-Feb-08 02:52 UTC
[llvm-dev] [6.0.0 Release] Release Candidate 2 tagged
All zig tests passed with 6.0.0-rc2. I noticed that my ELF debug-info loading code no longer finds source information, but this was also true for 6.0.0-rc1, and it's probably a dwarf feature that my code should be updated to support. I'll investigate and report back. On Wed, Feb 7, 2018 at 3:51 PM, Hans Wennborg via llvm-dev < llvm-dev at lists.llvm.org> wrote:> Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries. > > Thanks, > Hans > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180207/e626efae/attachment.html>
Hans Wennborg via llvm-dev
2018-Feb-08 10:28 UTC
[llvm-dev] [6.0.0 Release] Release Candidate 2 tagged
On Wed, Feb 7, 2018 at 9:51 PM, Hans Wennborg <hans at chromium.org> wrote:> Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries.Windows binaries are ready: $ sha1sum LLVM-6.0.0-rc2-win*.exe 53440640d7218497e2df43be4f31c08ace953bb3 LLVM-6.0.0-rc2-win32.exe cd8332062e25e03d2a4ed9a2c10613569a62633a LLVM-6.0.0-rc2-win64.exe They were built with the attached batch file. -------------- next part -------------- A non-text attachment was scrubbed... Name: build_llvm_600._bat_ Type: application/octet-stream Size: 4756 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180208/0f0192d3/attachment.obj>
NAKAMURA Takumi via llvm-dev
2018-Feb-08 11:31 UTC
[llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
FYI, unofficial CentOS6 RPMs are there. https://github.com/llvm-project/llvm-project-20170507/releases/tag/release_600_rc2 On Thu, Feb 8, 2018 at 5:52 AM Hans Wennborg via Release-testers < release-testers at lists.llvm.org> wrote:> Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries. > > Thanks, > Hans > _______________________________________________ > 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/20180208/5e19b52b/attachment.html>
Dimitry Andric via llvm-dev
2018-Feb-08 21:43 UTC
[llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:> > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries.Built, tested and uploaded: SHA256 (clang+llvm-6.0.0-rc2-amd64-unknown-freebsd10.tar.xz) = 1334db5949ec0c78cd6e9b798f0b397fe9e99240d98bcfc834e4410258b98372 SHA256 (clang+llvm-6.0.0-rc2-i386-unknown-freebsd10.tar.xz) = a7c0b1e4cfe3d608ee77472c7f17fe6b9493c7259aca80fcdd3b8a4fe49ad92d On amd64-freebsd10 there were 896 unexpected test failures: Expected Passes : 45004 Expected Failures : 186 Unsupported Tests : 2939 Unexpected Failures: 896 On i386-freebsd10 there were 619 unexpected test failures: Expected Passes : 43849 Expected Failures : 195 Unsupported Tests : 1954 Unexpected Failures: 619 At least the i386 version looks quite a bit better, down from 1773 to 619 test failures. :) -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/20180208/9421c9ae/attachment.sig>
Diana Picus via llvm-dev
2018-Feb-09 07:41 UTC
[llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
Uploaded ARM & AArch64: 929794f931a075b9981ac0b3828b74ff0a78c541 clang+llvm-6.0.0-rc2-aarch64-linux-gnu.tar.xz e1bebfc9c6dbbbdac3be0d629850442a0418b242 clang+llvm-6.0.0-rc2-armv7a-linux-gnueabihf.tar.xz The good news is that the previous issues have been fixed, the bad news is there are two new ones: PR36313 on AArch64 (failures in openmp tests) PR34182 on ARM (libcxxabi, we've seen this before in 5.0.0 but it was reverted on the release branch; I'm really sorry that I missed this in rc1, it got lost among all the tautological compare failures) Cheers, Diana On 8 February 2018 at 22:43, Dimitry Andric via Release-testers <release-testers at lists.llvm.org> wrote:> On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >> Please test, let me know how it goes, and upload binaries. > > Built, tested and uploaded: > > SHA256 (clang+llvm-6.0.0-rc2-amd64-unknown-freebsd10.tar.xz) = 1334db5949ec0c78cd6e9b798f0b397fe9e99240d98bcfc834e4410258b98372 > SHA256 (clang+llvm-6.0.0-rc2-i386-unknown-freebsd10.tar.xz) = a7c0b1e4cfe3d608ee77472c7f17fe6b9493c7259aca80fcdd3b8a4fe49ad92d > > On amd64-freebsd10 there were 896 unexpected test failures: > > Expected Passes : 45004 > Expected Failures : 186 > Unsupported Tests : 2939 > Unexpected Failures: 896 > > On i386-freebsd10 there were 619 unexpected test failures: > > Expected Passes : 43849 > Expected Failures : 195 > Unsupported Tests : 1954 > Unexpected Failures: 619 > > At least the i386 version looks quite a bit better, down from 1773 to 619 test failures. :) > > -Dimitry > > > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >
Sylvestre Ledru via llvm-dev
2018-Feb-09 08:52 UTC
[llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
Hello, On 07/02/2018 21:51, Hans Wennborg via Release-testers wrote:> Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries.Looks great on Debian. Bug 36051 (arm64 build issue) has been fixed. We did a rebuild of the Debian archive using 6.0rc1. I need to investigate the results but for now, I haven't seen anything crazy except a bug with qmake [1] (but not a regression on the clang side as I have the same issue with 5.0) Cheers, Sylvestre [1] https://bugreports.qt.io/browse/QTBUG-62531
Hans Wennborg via llvm-dev
2018-Feb-09 09:20 UTC
[llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote:> On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >> Please test, let me know how it goes, and upload binaries. > > Built, tested and uploaded: > > SHA256 (clang+llvm-6.0.0-rc2-amd64-unknown-freebsd10.tar.xz) = 1334db5949ec0c78cd6e9b798f0b397fe9e99240d98bcfc834e4410258b98372 > SHA256 (clang+llvm-6.0.0-rc2-i386-unknown-freebsd10.tar.xz) = a7c0b1e4cfe3d608ee77472c7f17fe6b9493c7259aca80fcdd3b8a4fe49ad92d > > On amd64-freebsd10 there were 896 unexpected test failures: > > Expected Passes : 45004 > Expected Failures : 186 > Unsupported Tests : 2939 > Unexpected Failures: 896 > > On i386-freebsd10 there were 619 unexpected test failures: > > Expected Passes : 43849 > Expected Failures : 195 > Unsupported Tests : 1954 > Unexpected Failures: 619 > > At least the i386 version looks quite a bit better, down from 1773 to 619 test failures. :)What are all these test failures? Does it seems like they have a common root cause and do we have a bug for it?
Michał Górny via llvm-dev
2018-Feb-09 16:00 UTC
[llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
W dniu śro, 07.02.2018 o godzinie 21∶51 +0100, użytkownik Hans Wennborg via Release-testers napisał:> Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries. >RC2 looks much better on Gentoo. The only remaining failures are LLDB (as usual) and compiler-rt [1]. I've pushed the ebuilds without keywords for brave users who want to play with them. [1]:https://bugs.llvm.org/show_bug.cgi?id=36065 -- Best regards, Michał Górny
Jonas Hahnfeld via llvm-dev
2018-Feb-13 09:36 UTC
[llvm-dev] [6.0.0 Release] Release Candidate 2 tagged
Am 2018-02-07 21:51, schrieb Hans Wennborg via llvm-dev:> Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries.Hi Hans, I can't build the documentation: <<<>>>/docs/ReleaseNotes.rst:91: WARNING: Title underline too short. Changes to the Hexagon Target ------------------------- (I think there are some more errors in ReleaseNotes.rst...) This brings me to the question which versions of sphinx LLVM officially supports? Regards, Jonas
Hans Wennborg via llvm-dev
2018-Feb-13 09:46 UTC
[llvm-dev] [6.0.0 Release] Release Candidate 2 tagged
On Tue, Feb 13, 2018 at 10:36 AM, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote:> Am 2018-02-07 21:51, schrieb Hans Wennborg via llvm-dev: >> >> Dear testers, >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >> Please test, let me know how it goes, and upload binaries. > > > Hi Hans, > > I can't build the documentation: > <<<>>>/docs/ReleaseNotes.rst:91: WARNING: Title underline too short. > > Changes to the Hexagon Target > -------------------------Sorry, I noticed that just after I put in the tag. It's been fixed now. There are more warnings, especially in some auto-generated files, but they look benign. I use -DSPHINX_WARNINGS_AS_ERRORS=OFF for my builds.> (I think there are some more errors in ReleaseNotes.rst...) > This brings me to the question which versions of sphinx LLVM officially > supports?I don't know if there's an officially supported version. I try to fix the warnings I see, and will go through especially the release notes before releasing, but I'm not sure we'll ever be warning clean. Thanks, Hans
Simon Dardis via llvm-dev
2018-Feb-13 21:57 UTC
[llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
Hi Hans,
I'm seeing one unexpected failure:
libc++ ::
std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp
Test logs show:
Standard Error:
--
terminating with uncaught exception of type std::length_error: basic_string
--
but only on my big endian MIPS machine. I have filed PR36373 for the above
failure.
I've looked at the failures from Msan from the previous rc candidate, and
have been unable to reproduce them. What
I have seen is that the observed test failures from rc1, rc1 investigations and
rc2 are transient.
Binaries uploaded.
SHA256(clang+llvm-6.0.0-rc2-mipsel-linux-gnu.tar.xz)=
0e446f60a1649680a49b048ad1429d4e327d1839dbbc8b34f1bd81e3277a98ee
SHA256(clang+llvm-6.0.0-rc2-mips-linux-gnu.tar.xz)=
bdec9b0fe00cfdeefe53b8e471b9266ad9a99dfd10eded5e078026f67a38650a
SHA256(clang+llvm-6.0.0-rc2-x86_64-linux-gnu-debian8.tar.xz)=
e6a281885d2f0fbc4e00bdc34803f67bb756f19badef3f24ed3738b2244c57cc
Thanks,
Simon
________________________________________
From: Release-testers [release-testers-bounces at lists.llvm.org] on behalf of
Hans Wennborg via Release-testers [release-testers at lists.llvm.org]
Sent: Wednesday, February 7, 2018 8:51 PM
To: Release-testers
Cc: llvm-dev; cfe-dev; openmp-dev (openmp-dev at lists.llvm.org); LLDB Dev
Subject: [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
Dear testers,
There's been a lot of merges since rc1, and hopefully the tests are in
a better state now.
6.0.0-rc2 was just tagged, after r324506.
Please test, let me know how it goes, and upload binaries.
Thanks,
Hans
_______________________________________________
Release-testers mailing list
Release-testers at lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
Hans Wennborg via llvm-dev
2018-Feb-14 10:10 UTC
[llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
Thanks! I've added the binaries to http://prereleases.llvm.org/6.0.0/ On Tue, Feb 13, 2018 at 10:57 PM, Simon Dardis <Simon.Dardis at mips.com> wrote:> Hi Hans, > > I'm seeing one unexpected failure: > > libc++ :: std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp > > Test logs show: > > Standard Error: > -- > terminating with uncaught exception of type std::length_error: basic_string > -- > > but only on my big endian MIPS machine. I have filed PR36373 for the above failure. > > I've looked at the failures from Msan from the previous rc candidate, and have been unable to reproduce them. What > I have seen is that the observed test failures from rc1, rc1 investigations and rc2 are transient. > > Binaries uploaded. > > SHA256(clang+llvm-6.0.0-rc2-mipsel-linux-gnu.tar.xz)= 0e446f60a1649680a49b048ad1429d4e327d1839dbbc8b34f1bd81e3277a98ee > SHA256(clang+llvm-6.0.0-rc2-mips-linux-gnu.tar.xz)= bdec9b0fe00cfdeefe53b8e471b9266ad9a99dfd10eded5e078026f67a38650a > SHA256(clang+llvm-6.0.0-rc2-x86_64-linux-gnu-debian8.tar.xz)= e6a281885d2f0fbc4e00bdc34803f67bb756f19badef3f24ed3738b2244c57cc > > Thanks, > Simon > ________________________________________ > From: Release-testers [release-testers-bounces at lists.llvm.org] on behalf of Hans Wennborg via Release-testers [release-testers at lists.llvm.org] > Sent: Wednesday, February 7, 2018 8:51 PM > To: Release-testers > Cc: llvm-dev; cfe-dev; openmp-dev (openmp-dev at lists.llvm.org); LLDB Dev > Subject: [Release-testers] [6.0.0 Release] Release Candidate 2 tagged > > Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries. > > Thanks, > Hans > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers