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

2016-01-21 Thread Eric Fiselier via lldb-dev 
On Wed, Jan 20, 2016 at 1:18 PM, Dimitry Andric via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> On 20 Jan 2016, at 18:23, Hans Wennborg  wrote:
> >
> > On Wed, Jan 20, 2016 at 5:25 AM, Dimitry Andric 
> wrote:
> >> Unfortunately I'm having lots of trouble with rc1 at this point:
> >> * libcxxabi can't build, because it requires unwind.h, which we do not
> yet have on FreeBSD 10.x (Ed Maste is working on it for 11.x, but that is
> not ready for general consumption).
> >> * The test-release.sh script has no option to disable only libcxxabi,
> you can only disable libcxx, libcxxabi and libunwind together (maybe this
> can be improved)
> >
> > Yes, I'd be happy to take a patch for this, or I suppose you could
> > just hack it out locally when building.
>
> It's not terribly important right now, as libcxx isn't succeeding its
> tests anyway.  I can locally hack it in, but I hope I won't forget it
> later. :)
>
>
> >> * Last time I hand-built libcxx, it still had a lot of test failures in
> the locale parts, but I haven't had time to investigate.
> >
> > Did we have that for 3.7 too?
>
> With 3.7, we used autoconf builds for FreeBSD, and that skipped libcxx
> altogether.  I did a few builds by hand, and I remember I saw similar
> failures.  This is just something that nobody (from FreeBSD) has seriously
> looked at, and I never had the time for it.  There are only so much hours
> in a day...
>
> For example, recently with trunk r256945, I saw these:
>
> Failing Tests (39):
> libc++ :: std/depr/depr.c.headers/stddef_h.pass.cpp
> libc++ :: std/depr/depr.c.headers/wchar_h.pass.cpp
> libc++ :: std/language.support/support.types/max_align_t.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.collate/locale.collate.byname/compare.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.collate/locale.collate.byname/transform.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.ctype/locale.ctype.byname/tolower_1.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.ctype/locale.ctype.byname/tolower_many.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.ctype/locale.ctype.byname/toupper_1.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.ctype/locale.ctype.byname/toupper_many.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_fr_FR.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_ru_RU.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_zh_CN.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.money.put/locale.money.put.members/put_long_double_fr_FR.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.money.put/locale.money.put.members/put_long_double_ru_RU.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.money.put/locale.money.put.members/put_long_double_zh_CN.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/curr_symbol.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/grouping.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/neg_format.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/pos_format.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/thousands_sep.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.time/locale.time.get.byname/get_date.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.time/locale.time.get.byname/get_date_wide.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.time/locale.time.get.byname/get_one.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.time/locale.time.get.byname/get_one_wide.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.time/locale.time.put.byname/put1.pass.cpp
> libc++ ::
> std/localization/locale.categories/facet.numpunct/locale.numpunct.byname/grouping.pass.cpp
> libc++ ::
> std/localization/locale.categories/facet.numpunct/locale.numpunct.byname/thousands_sep.pass.cpp
> libc++ :: std/re/re.alg/re.alg.match/basic.pass.cpp
> libc++ :: std/re/re.alg/re.alg.match/ecma.pass.cpp
> libc++ :: std/re/re.alg/re.alg.match/extended.pass.cpp
> libc++ :: std/re/re.alg/re.alg.search/awk.pass.cpp
> libc++ :: std/re/re.alg/re.alg.search/basic.pass.cpp
> libc++ :: std/re/re.alg/re.alg.search/ecma.pass.cpp
> libc++ :: std/re/re.alg/re.alg.search/extended.pass.cpp
>

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

2016-01-21 Thread Eric Fiselier via lldb-dev 
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.


> 
> 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  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  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-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [Attn: Bot Owners!] Raising CMake minimum version to 3.4.3

2016-05-24 Thread Eric Fiselier via lldb-dev 
Upgraded the libc++ bots.

On Tue, May 24, 2016 at 2:54 PM, Chris Bieneman via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> Meant to send this yesterday, but I want to remind everyone that we’re
> going to be raising the CMake minimum version to 3.4.3 next week.
>
> If you maintain bots please ensure that your bots are updated by end of
> day 5/29 so that we can move on 5/30 (next Monday).
>
> I have already heard from most bot owners either saying they had made the
> change, or scheduled to make it.
>
> If you have any questions or concerns please let me know.
>
> Thank you,
> -Chris
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

2017-03-04 Thread Eric Fiselier via lldb-dev 
On Fri, Mar 3, 2017 at 9:05 AM, Renato Golin 
wrote:

> On 2 March 2017 at 19:47, Hans Wennborg via Release-testers
>  wrote:
> > Hello testers,
> >
> > 4.0.0-rc3 was just tagged from the branch at r296762.
>
> ARM looks good, bd3c31f080a016409179fa8cb69da4e2fa14c951
> clang+llvm-4.0.0-rc3-armv7a-linux-gnueabihf.tar.xz
>
> AArch64 has a libc++ error we did not see on RC2:
>
> libc++ :: std/thread/thread.condition/thread.condition.condvarany/wait
> _for.pass.cpp
>
> wait_for.pass.cpp.exe:
> /home/renato.golin/devel/llvm/release/rc3/llvm.src/projects/
> libcxx/test/std/thread/thread.condition/thread.condition.con
> dvarany/wait_for.pass.cpp:58:
> void f(): Assertion `t1 - t0 - milliseconds(250) < milliseconds(50)'
> failed.
>
> Copying Eric and Marshall to see if they know of any back-ported
> commit that could cause this or if that's just the test's own
> instability (which seems to be the case).
>

Nothing relevant to this test has changed since the initial 4.0 branch. I
think it's safe to assume
the test is flakey, (Although I've never seen this specific test timeout
before)



>
> Anyway, binaries uploaded: 9356d607c68fbf8de56c03bde70c2964a794d26e
> clang+llvm-4.0.0-rc3-aarch64-linux-gnu.tar.xz
>
>
> > This is a release candidate in the real sense: if no major issues show
> > up with this one, it is the version that will be released.
>
> There is one rename that will land on trunk that needs to be announced
> on 4.0's release notes (https://reviews.llvm.org/D30510), but this
> won't need a new re-spin, just an update on the release notes before
> the final tag.
>
> cheers,
> --renato
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

2019-02-10 Thread Eric Fiselier via lldb-dev 
I'll take a look at this

On Fri., Feb. 8, 2019, 12:53 p.m. Paweł Sikora via cfe-dev, <
cfe-...@lists.llvm.org> wrote:

> - Oryginalna wiadomość -
> > Dear testers,
> >
> > 8.0.0-rc2 has been tagged from the release_80 branch at r353413.
>
> Hi,
>
> i've noticed a compile error with rc2 and libc++ (release_80 @svn). looks
> similar to https://bugs.llvm.org/show_bug.cgi?id=40559
>
>
> (...)/clang++ -fPIC -target x86_64-linux-gnu --sysroot=(...) -march=x86-64
> -fuse-ld=lld -D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR
> -D_LIBCPP_ENABLE_CXX17_REMOVED_BINDERS -stdlib=libc++ -std=gnu++1z
> -flto=thin
> (...)
> In file included from
> (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/string:500:
> In file included from
> (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/string_view:176:
> In file included from
> (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/__string:56:
> In file included from
> (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/algorithm:640:
> In file included from
> (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/initializer_list:47:
> In file included from
> (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/cstddef:110:
>
> (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/type_traits:740:56:
> error: _Float16 is not supported on this target
> template <>  struct __libcpp_is_floating_point<_Float16>:
> public true_type {};
>^
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev