public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
* make check inside docker container
@ 2018-02-28 14:27 James E. King, III
  2018-02-28 17:07 ` Carlos O'Donell
  0 siblings, 1 reply; 2+ messages in thread
From: James E. King, III @ 2018-02-28 14:27 UTC (permalink / raw)
  To: libc-help

I am putting together a Travis CI build environment for glibc that uses a
docker container (mostly to automate the Coverity Scan, but also to get
code coverage results), and a number of tests are failing.  I was wondering
if anyone can spot an easy fix, for example perhaps I am missing a debian
package I need.  (Ubuntu Artful is the base).  It looks like a bunch of
things in nptl are failing.  Here are the tests that are failing:

FAIL: debug/tst-backtrace2
FAIL: debug/tst-backtrace3
FAIL: debug/tst-backtrace4
FAIL: debug/tst-backtrace5
FAIL: debug/tst-backtrace6
FAIL: dlfcn/bug-atexit3
FAIL: elf/check-abi-libc
UNSUPPORTED: elf/tst-audit10
UNSUPPORTED: elf/tst-avx512
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
FAIL: intl/tst-gettext
UNSUPPORTED: math/test-double-libmvec-alias-avx512
UNSUPPORTED: math/test-double-libmvec-alias-avx512-main
UNSUPPORTED: math/test-double-libmvec-sincos-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512-main
UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
UNSUPPORTED: misc/tst-pkey
UNSUPPORTED: nptl/test-cond-printers
UNSUPPORTED: nptl/test-condattr-printers
UNSUPPORTED: nptl/test-mutex-printers
UNSUPPORTED: nptl/test-mutexattr-printers
UNSUPPORTED: nptl/test-rwlock-printers
UNSUPPORTED: nptl/test-rwlockattr-printers
FAIL: nptl/tst-basic3
FAIL: nptl/tst-basic4
FAIL: nptl/tst-cancel-self
FAIL: nptl/tst-cancel-self-cancelstate
FAIL: nptl/tst-cancel-self-canceltype
FAIL: nptl/tst-cancel-self-testcancel
FAIL: nptl/tst-cancel1
FAIL: nptl/tst-cancel10
FAIL: nptl/tst-cancel11
FAIL: nptl/tst-cancel12
FAIL: nptl/tst-cancel13
FAIL: nptl/tst-cancel14
FAIL: nptl/tst-cancel15
FAIL: nptl/tst-cancel16
FAIL: nptl/tst-cancel17
FAIL: nptl/tst-cancel18
FAIL: nptl/tst-cancel2
FAIL: nptl/tst-cancel20
FAIL: nptl/tst-cancel21
FAIL: nptl/tst-cancel22
FAIL: nptl/tst-cancel23
FAIL: nptl/tst-cancel24
FAIL: nptl/tst-cancel25
FAIL: nptl/tst-cancel3
FAIL: nptl/tst-cancel4
FAIL: nptl/tst-cancel4_1
FAIL: nptl/tst-cancel4_2
FAIL: nptl/tst-cancel5
FAIL: nptl/tst-cancel6
FAIL: nptl/tst-cancel7
FAIL: nptl/tst-cancel8
FAIL: nptl/tst-cancel9
FAIL: nptl/tst-cancelx10
FAIL: nptl/tst-cancelx11
FAIL: nptl/tst-cancelx12
FAIL: nptl/tst-cancelx13
FAIL: nptl/tst-cancelx14
FAIL: nptl/tst-cancelx15
FAIL: nptl/tst-cancelx16
FAIL: nptl/tst-cancelx17
FAIL: nptl/tst-cancelx18
FAIL: nptl/tst-cancelx2
FAIL: nptl/tst-cancelx20
FAIL: nptl/tst-cancelx21
FAIL: nptl/tst-cancelx3
FAIL: nptl/tst-cancelx4
FAIL: nptl/tst-cancelx5
FAIL: nptl/tst-cancelx6
FAIL: nptl/tst-cancelx7
FAIL: nptl/tst-cancelx8
FAIL: nptl/tst-cancelx9
FAIL: nptl/tst-cleanup0
FAIL: nptl/tst-cleanup0-cmp
FAIL: nptl/tst-cleanup1
FAIL: nptl/tst-cleanup3
FAIL: nptl/tst-cleanup4
FAIL: nptl/tst-cleanupx0
FAIL: nptl/tst-cleanupx1
FAIL: nptl/tst-cleanupx3
FAIL: nptl/tst-cleanupx4
FAIL: nptl/tst-cond-except
FAIL: nptl/tst-cond22
FAIL: nptl/tst-cond25
FAIL: nptl/tst-cond7
FAIL: nptl/tst-cond8
FAIL: nptl/tst-exec5
FAIL: nptl/tst-execstack
FAIL: nptl/tst-exit2
FAIL: nptl/tst-exit3
FAIL: nptl/tst-fini1
FAIL: nptl/tst-join1
FAIL: nptl/tst-join5
FAIL: nptl/tst-join6
FAIL: nptl/tst-key3
FAIL: nptl/tst-minstack-cancel
FAIL: nptl/tst-minstack-exit
FAIL: nptl/tst-minstack-throw
FAIL: nptl/tst-mutex8
FAIL: nptl/tst-mutexpi8
FAIL: nptl/tst-once3
FAIL: nptl/tst-once4
FAIL: nptl/tst-oncex3
FAIL: nptl/tst-oncex4
FAIL: nptl/tst-robust1
FAIL: nptl/tst-robust2
FAIL: nptl/tst-robust3
FAIL: nptl/tst-robust4
FAIL: nptl/tst-robust5
FAIL: nptl/tst-robust6
FAIL: nptl/tst-robust7
FAIL: nptl/tst-robustpi1
FAIL: nptl/tst-robustpi2
FAIL: nptl/tst-robustpi3
FAIL: nptl/tst-robustpi4
FAIL: nptl/tst-robustpi5
FAIL: nptl/tst-robustpi6
FAIL: nptl/tst-robustpi7
FAIL: nptl/tst-sem11
FAIL: nptl/tst-sem12
FAIL: nptl/tst-sem16
FAIL: nptl/tst-stack4
FAIL: nptl/tst-thread-exit-clobber
FAIL: nptl/tst-thread_local1
FAIL: nptl/tst-tsd5
FAIL: nss/tst-cancel-getpwuid_r
FAIL: posix/tst-getopt-cancel
FAIL: rt/tst-cpuclock2
FAIL: rt/tst-mqueue8
FAIL: rt/tst-mqueue8x
FAIL: rt/tst-shm-cancel
FAIL: stdlib/tst-quick_exit
FAIL: stdlib/tst-thread-quick_exit
Summary of test results:
    120 FAIL
   5606 PASS
     15 UNSUPPORTED
     16 XFAIL
      2 XPASS
Makefile:302: recipe for target 'tests' failed

These are the packages I put into the container:

FROM buildpack-deps:artful-scm

RUN apt-get update && \
    apt-get dist-upgrade -y

RUN apt-get install -y --no-install-recommends \
      apt \
      apt-transport-https \
      apt-utils \
      bash-completion \
      binutils \
      bison \
      build-essential \
      ca-certificates \
      g++-7 \
      g++-multilib \
      gawk \
      gcc-7 \
      gcc-multilib \
      gdb \
      gettext \
      libgd-dev \
      make \
      perl \
      software-properties-common \
      texinfo \
      valgrind \
      vim

Originally I had 124 failures and I added gcc-multilib and g++-multilib and
that brought it down to 120.

I am using this command to run a bash shell and then run configure and
build:

docker run --privileged --security-opt seccomp=unconfined --net=host -v
$(pwd):/develop -it <tag> /bin/bash

(container)# mkdir /stage
(container)# mkdir /install
(container)# cd /stage
(container)# /develop/configure --prefix=/install
(container)# make V=0 -j3

Has anybody tried this yet and/or have any suggestions?  Know of any
packages I forgot to add?

Thanks,

Jim

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: make check inside docker container
  2018-02-28 14:27 make check inside docker container James E. King, III
@ 2018-02-28 17:07 ` Carlos O'Donell
  0 siblings, 0 replies; 2+ messages in thread
From: Carlos O'Donell @ 2018-02-28 17:07 UTC (permalink / raw)
  To: James E. King, III, libc-help

On 02/28/2018 06:27 AM, James E. King, III wrote:
> I am putting together a Travis CI build environment for glibc that uses a
> docker container (mostly to automate the Coverity Scan, but also to get
> code coverage results), and a number of tests are failing.  I was wondering
> if anyone can spot an easy fix, for example perhaps I am missing a debian
> package I need.  (Ubuntu Artful is the base).  It looks like a bunch of
> things in nptl are failing.  Here are the tests that are failing:
> 
> FAIL: debug/tst-backtrace2
> FAIL: debug/tst-backtrace3
> FAIL: debug/tst-backtrace4
> FAIL: debug/tst-backtrace5
> FAIL: debug/tst-backtrace6

Missing libgcc.so?

> FAIL: dlfcn/bug-atexit3
> FAIL: elf/check-abi-libc

This is serious, what are the results?

> UNSUPPORTED: elf/tst-audit10
> UNSUPPORTED: elf/tst-avx512
> XPASS: elf/tst-protected1a
> XPASS: elf/tst-protected1b
> FAIL: intl/tst-gettext
> UNSUPPORTED: math/test-double-libmvec-alias-avx512
> UNSUPPORTED: math/test-double-libmvec-alias-avx512-main
> UNSUPPORTED: math/test-double-libmvec-sincos-avx512
> UNSUPPORTED: math/test-float-libmvec-alias-avx512
> UNSUPPORTED: math/test-float-libmvec-alias-avx512-main
> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
> UNSUPPORTED: misc/tst-pkey
> UNSUPPORTED: nptl/test-cond-printers
> UNSUPPORTED: nptl/test-condattr-printers
> UNSUPPORTED: nptl/test-mutex-printers
> UNSUPPORTED: nptl/test-mutexattr-printers
> UNSUPPORTED: nptl/test-rwlock-printers
> UNSUPPORTED: nptl/test-rwlockattr-printers
> FAIL: nptl/tst-basic3
> FAIL: nptl/tst-basic4
> FAIL: nptl/tst-cancel-self
> FAIL: nptl/tst-cancel-self-cancelstate
> FAIL: nptl/tst-cancel-self-canceltype
> FAIL: nptl/tst-cancel-self-testcancel
> FAIL: nptl/tst-cancel1
> FAIL: nptl/tst-cancel10
> FAIL: nptl/tst-cancel11
> FAIL: nptl/tst-cancel12
> FAIL: nptl/tst-cancel13
> FAIL: nptl/tst-cancel14
> FAIL: nptl/tst-cancel15
> FAIL: nptl/tst-cancel16
> FAIL: nptl/tst-cancel17
> FAIL: nptl/tst-cancel18
> FAIL: nptl/tst-cancel2
> FAIL: nptl/tst-cancel20
> FAIL: nptl/tst-cancel21
> FAIL: nptl/tst-cancel22
> FAIL: nptl/tst-cancel23
> FAIL: nptl/tst-cancel24
> FAIL: nptl/tst-cancel25
> FAIL: nptl/tst-cancel3
> FAIL: nptl/tst-cancel4
> FAIL: nptl/tst-cancel4_1
> FAIL: nptl/tst-cancel4_2
> FAIL: nptl/tst-cancel5
> FAIL: nptl/tst-cancel6
> FAIL: nptl/tst-cancel7
> FAIL: nptl/tst-cancel8
> FAIL: nptl/tst-cancel9
> FAIL: nptl/tst-cancelx10
> FAIL: nptl/tst-cancelx11
> FAIL: nptl/tst-cancelx12
> FAIL: nptl/tst-cancelx13
> FAIL: nptl/tst-cancelx14
> FAIL: nptl/tst-cancelx15
> FAIL: nptl/tst-cancelx16
> FAIL: nptl/tst-cancelx17
> FAIL: nptl/tst-cancelx18
> FAIL: nptl/tst-cancelx2
> FAIL: nptl/tst-cancelx20
> FAIL: nptl/tst-cancelx21
> FAIL: nptl/tst-cancelx3
> FAIL: nptl/tst-cancelx4
> FAIL: nptl/tst-cancelx5
> FAIL: nptl/tst-cancelx6
> FAIL: nptl/tst-cancelx7
> FAIL: nptl/tst-cancelx8
> FAIL: nptl/tst-cancelx9

Again, missing libgcc, and probably libstdc++ static.

> FAIL: nptl/tst-cleanup0
> FAIL: nptl/tst-cleanup0-cmp
> FAIL: nptl/tst-cleanup1
> FAIL: nptl/tst-cleanup3
> FAIL: nptl/tst-cleanup4
> FAIL: nptl/tst-cleanupx0
> FAIL: nptl/tst-cleanupx1
> FAIL: nptl/tst-cleanupx3
> FAIL: nptl/tst-cleanupx4
> FAIL: nptl/tst-cond-except
> FAIL: nptl/tst-cond22
> FAIL: nptl/tst-cond25
> FAIL: nptl/tst-cond7
> FAIL: nptl/tst-cond8
> FAIL: nptl/tst-exec5
> FAIL: nptl/tst-execstack
> FAIL: nptl/tst-exit2
> FAIL: nptl/tst-exit3
> FAIL: nptl/tst-fini1
> FAIL: nptl/tst-join1
> FAIL: nptl/tst-join5
> FAIL: nptl/tst-join6
> FAIL: nptl/tst-key3
> FAIL: nptl/tst-minstack-cancel
> FAIL: nptl/tst-minstack-exit
> FAIL: nptl/tst-minstack-throw
> FAIL: nptl/tst-mutex8
> FAIL: nptl/tst-mutexpi8
> FAIL: nptl/tst-once3
> FAIL: nptl/tst-once4
> FAIL: nptl/tst-oncex3
> FAIL: nptl/tst-oncex4
> FAIL: nptl/tst-robust1
> FAIL: nptl/tst-robust2
> FAIL: nptl/tst-robust3
> FAIL: nptl/tst-robust4
> FAIL: nptl/tst-robust5
> FAIL: nptl/tst-robust6
> FAIL: nptl/tst-robust7
> FAIL: nptl/tst-robustpi1
> FAIL: nptl/tst-robustpi2
> FAIL: nptl/tst-robustpi3
> FAIL: nptl/tst-robustpi4
> FAIL: nptl/tst-robustpi5
> FAIL: nptl/tst-robustpi6
> FAIL: nptl/tst-robustpi7
> FAIL: nptl/tst-sem11
> FAIL: nptl/tst-sem12
> FAIL: nptl/tst-sem16
> FAIL: nptl/tst-stack4
> FAIL: nptl/tst-thread-exit-clobber
> FAIL: nptl/tst-thread_local1
> FAIL: nptl/tst-tsd5
> FAIL: nss/tst-cancel-getpwuid_r
> FAIL: posix/tst-getopt-cancel
> FAIL: rt/tst-cpuclock2
> FAIL: rt/tst-mqueue8
> FAIL: rt/tst-mqueue8x
> FAIL: rt/tst-shm-cancel
> FAIL: stdlib/tst-quick_exit
> FAIL: stdlib/tst-thread-quick_exit
> Summary of test results:
>     120 FAIL
>    5606 PASS
>      15 UNSUPPORTED
>      16 XFAIL
>       2 XPASS
> Makefile:302: recipe for target 'tests' failed
> 
> These are the packages I put into the container:
> 
> FROM buildpack-deps:artful-scm
> 
> RUN apt-get update && \
>     apt-get dist-upgrade -y
> 
> RUN apt-get install -y --no-install-recommends \
>       apt \
>       apt-transport-https \
>       apt-utils \
>       bash-completion \
>       binutils \
>       bison \
>       build-essential \
>       ca-certificates \
>       g++-7 \
>       g++-multilib \
>       gawk \
>       gcc-7 \
>       gcc-multilib \
>       gdb \
>       gettext \
>       libgd-dev \
>       make \
>       perl \
>       software-properties-common \
>       texinfo \
>       valgrind \
>       vim

Does this include static libstdc++? You will need that for several of the tests.

In general you need to look at the build log or the test result logs to see what
happened. Provided that information we can give more accurate suggestions.

-- 
Cheers,
Carlos.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-02-28 17:07 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-02-28 14:27 make check inside docker container James E. King, III
2018-02-28 17:07 ` Carlos O'Donell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).