[ACTIVITY] 30 March - 3 April 2020

[Christophe Lyon]

== 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 quickly fixed by upstream in ICF optimization.

* misc:
- infra fixes / troubleshooting / reviews

== Next ==
* FDPIC GDB
* GCC/cortex-M
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Broken libcxx-libcxxabi-libunwind bots due to Filesystem tests

[Louis Dionne]

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:

FAIL: libc++::assign.pass.cpp
FAIL: libc++::path.pass.cpp
FAIL: libc++::replace_filename.pass.cpp
FAIL: libc++::refresh.pass.cpp
FAIL: libc++::file_size.pass.cpp
FAIL: libc++::file_type_obs.pass.cpp
FAIL: libc++::hard_link_count.pass.cpp
FAIL: libc++::last_write_time.pass.cpp
FAIL: libc++::ctor.pass.cpp
FAIL: libc++::ctor.pass.cpp
FAIL: libc++::increment.pass.cpp
FAIL: libc++::exists.pass.cpp
FAIL: libc++::is_block_file.pass.cpp
FAIL: libc++::is_character_file.pass.cpp
FAIL: libc++::is_directory.pass.cpp
FAIL: libc++::is_empty.pass.cpp
FAIL: libc++::is_fifo.pass.cpp
FAIL: libc++::is_other.pass.cpp
FAIL: libc++::is_regular_file.pass.cpp
FAIL: libc++::is_socket.pass.cpp

Having seen some of these issues before, 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 check for failure to 
access some files for which there's no permission. This doesn't seem to work 
when run as root.

Can you work with us to resolve this issue?

Thanks,
Louis

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Duncan Exon Smith]

> 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 check for failure to access some files for which there's 
> no permission. This doesn't seem to work when run as root.

It seems like these tests could have a line like:
```
REQUIRES: -user=root
```
and libcxx's lit target could export a `user=root` feature when tests were 
being run as root.  WDYT?

WDYT?

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Louis Dionne]

> 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
>  
> 
> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux 
> 
> 
> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux 
> 
> 
> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions
>  
> 
> 
> They all fail on the test libcxx/test/libcxx/modules/stds_include.sh.cpp with 
> the following error:
> 
> <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: fatal error: 
> file '<...>/libcxx/include/type_traits' has been modified since the module 
> file '/ModuleCache/1E92AHT/std-1V9DLRO.pcm' was built
> #include 
>  ^
> <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: note: please 
> rebuild precompiled header '/ModuleCache/1E92AHT/std-1V9DLRO.pcm'
> 1 error generated.
> 
> 
> Our other bots are not failing, so I very strongly suspect this is not 
> because of the change itself, but rather some weirdness in your bot 
> configuration. For that reason, I will *not* revert the change (that would 
> likely not improve the situation anyway). Can you please collaborate with us 
> to understand and fix the issue?

Also, is there a Docker image used to run the bots? That is our preferred way 
of handling libc++/libc++abi bots, because that means anyone can reproduce the 
failures locally. If the bots don't require anything specific beyond the CMake 
configuration they're testing, you could even use our existing Docker images 
based on Debian.

Louis

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Failing libcxx-libcxxabi-libunwind bots

[Louis Dionne]

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/builders/libcxx-libcxxabi-libunwind-aarch64-linux

http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions

They all fail on the test libcxx/test/libcxx/modules/stds_include.sh.cpp with 
the following error:

<...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: fatal error: 
file '<...>/libcxx/include/type_traits' has been modified since the module file 
'/ModuleCache/1E92AHT/std-1V9DLRO.pcm' was built
#include 
 ^
<...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: note: please 
rebuild precompiled header '/ModuleCache/1E92AHT/std-1V9DLRO.pcm'
1 error generated.


Our other bots are not failing, so I very strongly suspect this is not because 
of the change itself, but rather some weirdness in your bot configuration. For 
that reason, I will *not* revert the change (that would likely not improve the 
situation anyway). Can you please collaborate with us to understand and fix the 
issue?

Thanks,
Louis

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Duncan Exon Smith]

> 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 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 check for failure to access some files for which 
>>> there's no permission. This doesn't seem to work when run as root.
>> 
>> It seems like these tests could have a line like:
>> ```
>> REQUIRES: -user=root
>> ```
>> and libcxx's lit target could export a `user=root` feature when tests were 
>> being run as root.  WDYT?
>> 
>> WDYT?
>> 
> 
> I think you mean `// UNSUPPORTED: -user=root`? Yes, I think it would make 
> sense. Either that or actually spend the time to make them work as root.

I meant `REQUIRES: !user=root`, I used the wrong negation.

> 
> FWIW, I think the root cause of the issue is that "traverse" permissions in 
> directories are not honoured when run as root:
> 
> root $ d=$(mktemp -d)
> root $ touch $d/foo
> root $ chmod 000 $d
> root $ stat $d/foo
> 16777221 234259215 -rw-r--r-- 1 root wheel 0 0 <...>
> 
> When I would expect:
> 
> ldionne $ d=$(mktemp -d)
> ldionne $ touch $d/foo
> ldionne $ chmod 000 $d
> ldionne $ stat $d/foo
> stat: <...>/tmp.JoY6Ixmo/foo: stat: Permission denied
> 
> Does that make sense? I didn't know 'root' had a free pass like that.
> 
> Louis

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Louis Dionne]

> 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 are known to fail when run as root, because 
>> some of them need to check for failure to access some files for which 
>> there's no permission. This doesn't seem to work when run as root.
> 
> It seems like these tests could have a line like:
> ```
> REQUIRES: -user=root
> ```
> and libcxx's lit target could export a `user=root` feature when tests were 
> being run as root.  WDYT?
> 
> WDYT?
> 

I think you mean `// UNSUPPORTED: -user=root`? Yes, I think it would make 
sense. Either that or actually spend the time to make them work as root.

FWIW, I think the root cause of the issue is that "traverse" permissions in 
directories are not honoured when run as root:

root $ d=$(mktemp -d)
root $ touch $d/foo
root $ chmod 000 $d
root $ stat $d/foo
16777221 234259215 -rw-r--r-- 1 root wheel 0 0 <...>

When I would expect:

ldionne $ d=$(mktemp -d)
ldionne $ touch $d/foo
ldionne $ chmod 000 $d
ldionne $ stat $d/foo
stat: <...>/tmp.JoY6Ixmo/foo: stat: Permission denied

Does that make sense? I didn't know 'root' had a free pass like that.

Louis

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Duncan Exon Smith]

> 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 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 check for failure to access some files for 
 which there's no permission. This doesn't seem to work when run as root.
>>> 
>>> It seems like these tests could have a line like:
>>> ```
>>> REQUIRES: -user=root
>>> ```
>>> and libcxx's lit target could export a `user=root` feature when tests were 
>>> being run as root.  WDYT?
>>> 
>>> WDYT?
>>> 
>> 
>> I think you mean `// UNSUPPORTED: -user=root`? Yes, I think it would make 
>> sense. Either that or actually spend the time to make them work as root.
> 
> I meant `REQUIRES: !user=root`, I used the wrong negation.

Although UNSUPPORTED is maybe more clear.

> 
>> 
>> FWIW, I think the root cause of the issue is that "traverse" permissions in 
>> directories are not honoured when run as root:
>> 
>> root $ d=$(mktemp -d)
>> root $ touch $d/foo
>> root $ chmod 000 $d
>> root $ stat $d/foo
>> 16777221 234259215 -rw-r--r-- 1 root wheel 0 0 <...>
>> 
>> When I would expect:
>> 
>> ldionne $ d=$(mktemp -d)
>> ldionne $ touch $d/foo
>> ldionne $ chmod 000 $d
>> ldionne $ stat $d/foo
>> stat: <...>/tmp.JoY6Ixmo/foo: stat: Permission denied
>> 
>> Does that make sense? I didn't know 'root' had a free pass like that.
>> 
>> Louis
> 
> ___
> libcxx-dev mailing list
> libcxx-...@lists.llvm.org 
> https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev 
> 
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Yvan Roux]

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.com/u/linaro

Thanks
Yvan

On Mon, 6 Apr 2020 at 10:08, Louis Dionne  wrote:

>
>
> > On Apr 2, 2020, at 13:28, Louis Dionne via libcxx-dev <
> libcxx-...@lists.llvm.org> 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
> <
> 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/builders/libcxx-libcxxabi-libunwind-armv8-linux>
> >
> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux
> <
> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux
> >
> >
> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions
> <
> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions
> >
> >
> > They all fail on the test libcxx/test/libcxx/modules/stds_include.sh.cpp
> with the following error:
> >
> > <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: fatal
> error: file '<...>/libcxx/include/type_traits' has been modified since the
> module file '/ModuleCache/1E92AHT/std-1V9DLRO.pcm' was built
> > #include 
> >  ^
> > <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: note:
> please rebuild precompiled header
> '/ModuleCache/1E92AHT/std-1V9DLRO.pcm'
> > 1 error generated.
> >
> >
> > Our other bots are not failing, so I very strongly suspect this is not
> because of the change itself, but rather some weirdness in your bot
> configuration. For that reason, I will *not* revert the change (that would
> likely not improve the situation anyway). Can you please collaborate with
> us to understand and fix the issue?
>
> Also, is there a Docker image used to run the bots? That is our preferred
> way of handling libc++/libc++abi bots, because that means anyone can
> reproduce the failures locally. If the bots don't require anything specific
> beyond the CMake configuration they're testing, you could even use our
> existing Docker images based on Debian.
>
> Louis
>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/linaro-toolchain
>
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Yvan Roux]

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, at 13:10, Duncan Exon Smith via libcxx-dev <
> libcxx-...@lists.llvm.org> wrote:
> >
> >
> >
> >> On 2020-Apr-02, at 11:23, Louis Dionne  ldio...@apple.com>> 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 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 check for failure to access some files
> for which there's no permission. This doesn't seem to work when run as root.
> >>>
> >>> It seems like these tests could have a line like:
> >>> ```
> >>> REQUIRES: -user=root
> >>> ```
> >>> and libcxx's lit target could export a `user=root` feature when tests
> were being run as root.  WDYT?
> >>>
> >>> WDYT?
> >>>
> >>
> >> I think you mean `// UNSUPPORTED: -user=root`? Yes, I think it would
> make sense. Either that or actually spend the time to make them work as
> root.
> >
> > I meant `REQUIRES: !user=root`, I used the wrong negation.
>
> Although UNSUPPORTED is maybe more clear.
>
> >
> >>
> >> FWIW, I think the root cause of the issue is that "traverse"
> permissions in directories are not honoured when run as root:
> >>
> >> root $ d=$(mktemp -d)
> >> root $ touch $d/foo
> >> root $ chmod 000 $d
> >> root $ stat $d/foo
> >> 16777221 234259215 -rw-r--r-- 1 root wheel 0 0 <...>
> >>
> >> When I would expect:
> >>
> >> ldionne $ d=$(mktemp -d)
> >> ldionne $ touch $d/foo
> >> ldionne $ chmod 000 $d
> >> ldionne $ stat $d/foo
> >> stat: <...>/tmp.JoY6Ixmo/foo: stat: Permission denied
> >>
> >> Does that make sense? I didn't know 'root' had a free pass like that.
> >>
> >> Louis
> >
> > ___
> > libcxx-dev mailing list
> > libcxx-...@lists.llvm.org 
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev <
> https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/linaro-toolchain
>
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Yvan Roux]

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 remove these files at the end.
>
>
> Are you using some special CMake variable to point the build to that
> Module cache? If so, then it would be the responsibility of the bot to
> clean it up.
>

Nope, there is nothing special on cmake command line.

http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux/builds/1512/steps/cmake/logs/stdio

Yvan


>
> Louis
>
>
> All our bots run inside containers, they are available here
> https://hub.docker.com/u/linaro
>
> Thanks
> Yvan
>
> On Mon, 6 Apr 2020 at 10:08, Louis Dionne  wrote:
>
>>
>>
>> > On Apr 2, 2020, at 13:28, Louis Dionne via libcxx-dev <
>> libcxx-...@lists.llvm.org> 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
>>  <
>> 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/builders/libcxx-libcxxabi-libunwind-aarch64-linux
>>  <
>> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux
>> >
>> >
>> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions
>>  <
>> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions
>> >
>> >
>> > They all fail on the test
>> libcxx/test/libcxx/modules/stds_include.sh.cpp with the following error:
>> >
>> > <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: fatal
>> error: file '<...>/libcxx/include/type_traits' has been modified since the
>> module file '/ModuleCache/1E92AHT/std-1V9DLRO.pcm' was built
>> > #include 
>> >  ^
>> > <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: note:
>> please rebuild precompiled header
>> '/ModuleCache/1E92AHT/std-1V9DLRO.pcm'
>> > 1 error generated.
>> >
>> >
>> > Our other bots are not failing, so I very strongly suspect this is not
>> because of the change itself, but rather some weirdness in your bot
>> configuration. For that reason, I will *not* revert the change (that would
>> likely not improve the situation anyway). Can you please collaborate with
>> us to understand and fix the issue?
>>
>> Also, is there a Docker image used to run the bots? That is our preferred
>> way of handling libc++/libc++abi bots, because that means anyone can
>> reproduce the failures locally. If the bots don't require anything specific
>> beyond the CMake configuration they're testing, you could even use our
>> existing Docker images based on Debian.
>>
>> Louis
>>
>> ___
>> linaro-toolchain mailing list
>> linaro-toolchain@lists.linaro.org
>> https://lists.linaro.org/mailman/listinfo/linaro-toolchain
>
>
>
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Louis Dionne]

> 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 special CMake variable to point the build to that Module 
cache? If so, then it would be the responsibility of the bot to clean it up.

Louis

> 
> All our bots run inside containers, they are available here 
> https://hub.docker.com/u/linaro 
> 
> Thanks
> Yvan
> 
> On Mon, 6 Apr 2020 at 10:08, Louis Dionne  > wrote:
> 
> 
> > On Apr 2, 2020, at 13:28, Louis Dionne via libcxx-dev 
> > mailto:libcxx-...@lists.llvm.org>> 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
> >  
> > 
> >  
> >  >  
> > >
> > 
> > http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux 
> >  
> >  > >
> > 
> > http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux 
> > 
> >  
> >  > >
> > 
> > http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions
> >  
> > 
> >  
> >  >  
> > >
> > 
> > They all fail on the test libcxx/test/libcxx/modules/stds_include.sh.cpp 
> > with the following error:
> > 
> > <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: fatal error: 
> > file '<...>/libcxx/include/type_traits' has been modified since the module 
> > file '/ModuleCache/1E92AHT/std-1V9DLRO.pcm' was built
> > #include 
> >  ^
> > <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: note: please 
> > rebuild precompiled header '/ModuleCache/1E92AHT/std-1V9DLRO.pcm'
> > 1 error generated.
> > 
> > 
> > Our other bots are not failing, so I very strongly suspect this is not 
> > because of the change itself, but rather some weirdness in your bot 
> > configuration. For that reason, I will *not* revert the change (that would 
> > likely not improve the situation anyway). Can you please collaborate with 
> > us to understand and fix the issue?
> 
> Also, is there a Docker image used to run the bots? That is our preferred way 
> of handling libc++/libc++abi bots, because that means anyone can reproduce 
> the failures locally. If the bots don't require anything specific beyond the 
> CMake configuration they're testing, you could even use our existing Docker 
> images based on Debian.
> 
> Louis
> 
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org 
> https://lists.linaro.org/mailman/listinfo/linaro-toolchain 
> 
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

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

[Louis Dionne]

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  wrote:
> 
> 
> 
> 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 remove these files at the end.
> 
> Are you using some special CMake variable to point the build to that Module 
> cache? If so, then it would be the responsibility of the bot to clean it up.
> 
> Nope, there is nothing special on cmake command line.
> 
> http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux/builds/1512/steps/cmake/logs/stdio
>  
> 
> 
> Yvan
>  
> 
> Louis
> 
>> 
>> All our bots run inside containers, they are available here 
>> https://hub.docker.com/u/linaro 
>> 
>> Thanks
>> Yvan
>> 
>> On Mon, 6 Apr 2020 at 10:08, Louis Dionne > > wrote:
>> 
>> 
>> > On Apr 2, 2020, at 13:28, Louis Dionne via libcxx-dev 
>> > mailto:libcxx-...@lists.llvm.org>> 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
>> >  
>> > 
>> >  
>> > > >  
>> > >
>> > 
>> > http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux 
>> >  
>> > > > >
>> > 
>> > http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux 
>> > 
>> >  
>> > > >  
>> > >
>> > 
>> > http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions
>> >  
>> > 
>> >  
>> > > >  
>> > >
>> > 
>> > They all fail on the test libcxx/test/libcxx/modules/stds_include.sh.cpp 
>> > with the following error:
>> > 
>> > <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: fatal 
>> > error: file '<...>/libcxx/include/type_traits' has been modified since the 
>> > module file '/ModuleCache/1E92AHT/std-1V9DLRO.pcm' was built
>> > #include 
>> >  ^
>> > <...>/libcxx/test/libcxx/modules/stds_include.sh.cpp:28:2: note: 
>> > please rebuild precompiled header 
>> > '/ModuleCache/1E92AHT/std-1V9DLRO.pcm'
>> > 1 error generated.
>> > 
>> > 
>> > Our other bots are not failing, so I very strongly suspect this is not 
>> > because of the change itself, but rather some weirdness in your bot 
>> > configuration. For that reason, I will *not* revert the change (that would 
>> > likely not improve the situation anyway). Can you please collaborate with 
>> > us to understand and fix the issue?
>> 
>> Also, is there a Docker image used to run the bots? That is our preferred 
>> way of handling libc++/libc++abi bots, because that means anyone can 
>> reproduce the failures locally. If the bots don't require anything specific 
>> beyond the CMake configuration they're testing, you could even use our 
>> existing Docker images based on Debian.
>> 
>> Louis
>> 
>> ___
>> linaro-toolchain mailing list
>> linaro-toolchain@lists.linaro.org 
>> https://lists.linaro.org/mailman/listinfo/linaro-toolchain 
>> 

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain