Re: [libcxx-dev] Failing libcxx-libcxxabi-libunwind bots

Nevermind, it seems that this is a Clang bug instead. See: commit 62f3a9650a9f289a07a5f480764fb655178c2334 Author: Eric Fiselier Date: Sat Apr 4 03:18:01 2020 -0400 [libc++] Attempt to workaround module invalidation bug Cheers, Louis > On Apr 6, 2020, at 09:30, Yvan Roux

Re: [libcxx-dev] Failing libcxx-libcxxabi-libunwind bots

> On Apr 6, 2020, at 08:21, Yvan Roux wrote: > > Hi Louis, > > Yes the issue due to this directory /ModuleCache not being removed after > it is used or cleaned up at the beginning. So it's on our side or into the > test itself which doesn't remove these files at the end. Are you using some

Re: [libcxx-dev] Failing libcxx-libcxxabi-libunwind bots

On Mon, 6 Apr 2020 at 15:18, Louis Dionne wrote: > > > On Apr 6, 2020, at 08:21, Yvan Roux wrote: > > Hi Louis, > > Yes the issue due to this directory /ModuleCache not being removed > after it is used or cleaned up at the beginning. So it's on our side or > into the test itself which doesn't r

Re: [libcxx-dev] Broken libcxx-libcxxabi-libunwind bots due to Filesystem tests

Hi Louis and Duncan, Sorry the issue is indeed on our si8de, the bot is not run as run root, but some manual investigation last week accidentally created these files with root ownership, sorry for that. Thanks Yvan On Mon, 6 Apr 2020 at 10:09, Duncan Exon Smith wrote: > > > > On 2020-Apr-02,

Re: [libcxx-dev] Failing libcxx-libcxxabi-libunwind bots

Hi Louis, Yes the issue due to this directory /ModuleCache not being removed after it is used or cleaned up at the beginning. So it's on our side or into the test itself which doesn't remove these files at the end. All our bots run inside containers, they are available here https://hub.docker.co

Re: [libcxx-dev] Broken libcxx-libcxxabi-libunwind bots due to Filesystem tests

> On 2020-Apr-02, at 13:10, Duncan Exon Smith via libcxx-dev > wrote: > > > >> On 2020-Apr-02, at 11:23, Louis Dionne > > wrote: >> >> >> >>> On Apr 2, 2020, at 14:05, Duncan Exon Smith >> > wrote: >>> It looks like the followin

Re: [libcxx-dev] Broken libcxx-libcxxabi-libunwind bots due to Filesystem tests

> On Apr 2, 2020, at 14:05, Duncan Exon Smith wrote: > >> It looks like the following bots assigned to you started failing recently: > > I agree the bots should be fixed, but... > >> I strongly suspect this is due to the fact that your builder is running as >> root. Libc++'s filesystem tests

Re: [libcxx-dev] Broken libcxx-libcxxabi-libunwind bots due to Filesystem tests

> On 2020-Apr-02, at 11:23, Louis Dionne wrote: > > > >> On Apr 2, 2020, at 14:05, Duncan Exon Smith > > wrote: >> >>> It looks like the following bots assigned to you started failing recently: >> >> I agree the bots should be fixed, but... >> >>> I strongly su

Re: [libcxx-dev] Failing libcxx-libcxxabi-libunwind bots

> On Apr 2, 2020, at 13:28, Louis Dionne via libcxx-dev > wrote: > > Hi, > > It looks like several bots assigned to you started failing after e6a39f00e8d0 > was committed: > > > http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux-noexceptions > >

Failing libcxx-libcxxabi-libunwind bots

Hi, It looks like several bots assigned to you started failing after e6a39f00e8d0 was committed: http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux-noexceptions http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux http://lab.llvm.org:8011/bu

Broken libcxx-libcxxabi-libunwind bots due to Filesystem tests

Hi, It looks like the following bots assigned to you started failing recently: http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv7-linux http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv7-linux-noexceptions The failing tests are all filesystem tests:

Re: [libcxx-dev] Broken libcxx-libcxxabi-libunwind bots due to Filesystem tests

> It looks like the following bots assigned to you started failing recently: I agree the bots should be fixed, but... > I strongly suspect this is due to the fact that your builder is running as > root. Libc++'s filesystem tests are known to fail when run as root, because > some of them need to

[ACTIVITY] 30 March - 3 April 2020

== Progress == * GCC upstream validation: - reported a couple of failures/regressions * GCC: - comparing testsuite results for cortex-m3 and cortex-m33 with cortex-a9 to check what cortex-M problem there are. Spent a long time isolating a regression in CMSE tests. Filed PR94445 which was then qu