[cfe-dev] [3.8 Release] RC1 has been tagged

[Eric Fiselier via cfe-dev]

On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev <
cfe-dev at 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.


> ~~~~~~~~~~~~~~~~
> Failing Tests (27):
>     LLVM-Unit :: Support/SupportTests/ThreadPoolTest.Async
>     LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrier
>     LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrierArgs
>     LLVM-Unit :: Support/SupportTests/ThreadPoolTest.GetFuture
>     LLVM-Unit :: Support/SupportTests/ThreadPoolTest.PoolDestruction
>     MemorySanitizer :: Linux/obstack.cc
>     MemorySanitizer :: Linux/process_vm_readv.cc
>     MemorySanitizer :: fork.cc
>     MemorySanitizer :: iconv.cc
>     MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.fgetgrent_r
>     MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent
>     MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent_r
>     MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getpwent
>     MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getpwent_r
>     MemorySanitizer-Unit ::
> Msan-x86_64-with-call-Test/MemorySanitizer.fgetgrent_r
>     MemorySanitizer-Unit ::
> Msan-x86_64-with-call-Test/MemorySanitizer.getgrent
>     MemorySanitizer-Unit ::
> Msan-x86_64-with-call-Test/MemorySanitizer.getgrent_r
>     MemorySanitizer-Unit ::
> Msan-x86_64-with-call-Test/MemorySanitizer.getpwent
>     MemorySanitizer-Unit ::
> Msan-x86_64-with-call-Test/MemorySanitizer.getpwent_r
>     SanitizerCommon-Unit ::
> Sanitizer-x86_64-Test/SanitizerLinux.ThreadDescriptorSize
>     ThreadSanitizer :: Linux/mutex_robust.cc
>     ThreadSanitizer :: Linux/mutex_robust2.cc
>     ThreadSanitizer :: thread_name2.cc
>     libc++ :: std/depr/depr.c.headers/uchar_h.pass.cpp
>

This is caused because the system does not provide a uchar.h header.


>     libc++ ::
> std/localization/locale.categories/category.time/locale.time.get.byname/get_monthname.pass.cpp
>     libc++ ::
> std/localization/locale.categories/category.time/locale.time.get.byname/get_monthname_wide.pass.cpp
>


These are marked XFAIL on open-suse, They should probably be marked as
XFAIL on your platform as well.
Can you send me the output of Python's "platform.linux_distribution()"?


>     libc++abi :: cxa_thread_atexit_test.pass.cpp
>

Not sure about this failure. Can you send me the output?


>
>   Expected Passes    : 31153
>   Expected Failures  : 203
>   Unsupported Tests  : 518
>   Unexpected Failures: 27
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Uploads:
> 7b837b2c4b7884a4277b947b795948ecd983b0f3
>  clang+llvm-3.8.0-rc1-linux-x86_64-sles11.3.tar.xz
>
>
> On Tue, Jan 19, 2016 at 5:55 PM, Hans Wennborg <hans at chromium.org> wrote:
>
>> (cc'ing non-legacy llvm-dev this time; apologies if you get this
>> twice. Please don't reply-all to the first one.)
>>
>> On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> 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
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160121/8dcd10bd/attachment.html>