From: Mark Wielaard <mjw@redhat.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: libc-alpha@sourceware.org, tuliom@quites.com.br
Subject: Re: [glibc-buildbot] Add 'glibc-s390x-linux': 'marist-fedora-s390x' to builder_map.
Date: Wed, 05 Oct 2016 19:47:00 -0000 [thread overview]
Message-ID: <1475696860.21750.67.camel@redhat.com> (raw)
In-Reply-To: <20161004190107.4CDDF2C3B9D@topped-with-meat.com>
On Tue, 2016-10-04 at 12:01 -0700, Roland McGrath wrote:
> Merged.
Thanks. And now it triggers builds! It is already on its second one.
But some target steps seem to fail. I am wondering how to fix that so
the build gets green.
First there is the 'annotate' step which seems to fail because make
check isn't zero FAIL:
http://130.211.48.148:8080/builders/glibc-s390x-linux/builds/3/steps/annotate/logs/stdio
Summary of test results:
4 FAIL
2478 PASS
13 UNSUPPORTED
44 XFAIL
Makefile:353: recipe for target 'tests' failed
make[1]: Leaving directory '/home/mjw/glibc/build/glibc-s390x-linux/build/glibc'
make[1]: *** [tests] Error 1
Where the FAILS are:
FAIL: malloc/tst-malloc-thread-fail
FAIL: malloc/tst-mallocfork2
FAIL: posix/tst-getaddrinfo4
FAIL: timezone/tst-tzset
Can/should I ignore those (how?) or are these suspicious?
Then there is the 'check' target which fails as follows:
http://130.211.48.148:8080/builders/glibc-s390x-linux/builds/3/steps/check/logs/stdio
test -s /home/mjw/glibc/build/glibc-s390x-linux/build/build/rt/librt.so.phdrT
mv -f /home/mjw/glibc/build/glibc-s390x-linux/build/build/rt/librt.so.phdrT /home/mjw/glibc/build/glibc-s390x-linux/build/build/rt/librt.so.phdr
make[1]: *** [tests] Error 1
make[1]: Target 'check' not remade because of errors.
make[1]: Leaving directory '/home/mjw/glibc/build/glibc-s390x-linux/build/glibc'
Makefile:9: recipe for target 'check' failed
make: Leaving directory '/home/mjw/glibc/build/glibc-s390x-linux/build/build'
@@@STEP_FAILURE@@@
make: *** [check] Error 2
I cannot find anything that explains that failure in the stdio log.
Finally the 'check (clobber)' target fails apparently for the same
reason as the 'annotate' one.
Any advise on how to resolve these issues and turn the build green?
Thanks,
Mark
next prev parent reply other threads:[~2016-10-05 19:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 22:52 Mark Wielaard
2016-10-03 23:14 ` Carlos O'Donell
2016-10-03 23:31 ` Roland McGrath
2016-10-04 14:15 ` Mark Wielaard
2016-10-04 19:01 ` Roland McGrath
2016-10-05 19:47 ` Mark Wielaard [this message]
2016-10-05 20:13 ` Joseph Myers
2016-10-05 21:34 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1475696860.21750.67.camel@redhat.com \
--to=mjw@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=roland@hack.frob.com \
--cc=tuliom@quites.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).