This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Good mailing list to use to send out test results to


On Fri, Jul 15, 2016 at 12:21 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 07/15/2016 04:07 AM, Andrew Pinski wrote:
>>
>> Hi,
>>   I am doing a build automation of glibc on aarch64-linux-gnu (but not
>> using the buildbot scripts) and was wondering what is a good mailing
>> list where I can send the test results summary to.
>
>
> Before that, we need to figure out what's wrong with the build environment.
> :-/
>
>> A sample email would be:
>>
>> Subject: Glibc revision 2b6dbe669fa2e488b31286150e8cb6f7c0875847
>> testresults for aarch64-linux-gnu
>> FAIL: conform/POSIX/glob.h/linknamespace
>
>
> So far, we have seen this with excessive parallelization.  I stared about
> the makefile for a while, but could not identify the cause, so it's still
> not fixed.
>
>> FAIL: debug/tst-backtrace5
>> FAIL: debug/tst-backtrace6
>
>
> These are real failures, see the thread “tst-backtrace failures on AArch64”
> from 2014.
>
> The following need investigation:
>
>> FAIL: math/test-double
>> FAIL: math/test-double-finite
>> FAIL: math/test-float
>> FAIL: math/test-float-finite
>> FAIL: math/test-idouble
>> FAIL: math/test-ifloat

I will look into those soon; it could be trunk gcc is producing weird
results too.

>> FAIL: malloc/tst-malloc-thread-exit
>> FAIL: malloc/tst-malloc-thread-fail
>> FAIL: nptl/tst-cond16
>> FAIL: nptl/tst-cond17
>> FAIL: nptl/tst-cond20
>> FAIL: nptl/tst-dlsym1
>> FAIL: nptl/tst-robust8
>> FAIL: nptl/tst-robustpi8
>> FAIL: nptl/tst-rwlock16
>> FAIL: nptl/tst-sem14
>> FAIL: nptl/tst-stack4
>> FAIL: rt/tst-mqueue6

tst-cond16: pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion
`mutex->__data.__owner == 0' failed.
This non-math ones could be an issue with the ARMv8.1 LSE extensions
(I have to look to see if it is that or hw issue).
I will run one test without LSE to see if I get a failures there too.

>> FAIL: nptl/tst-thread_local1

nptl/tst-thread_local1 is due not having LD_LIBRARY_PATH set to
include the newly built toolchain's lib directory.

>> FAIL: nss/tst-nss-static
>
>
> The math failures may or may not go away with ULP regeneration.  The
> *robust* failures may be spurious.  The others may be genuine issues.
> Unfortunately, there is not sufficient detail in the output to start an
> investigation.
>
> With such a larger number of failures, such build reports are less useful
> than they could be.
>
> Florian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]