From: Stefan Liebler <stli@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] support: Introduce new subdirectory for test infrastructure
Date: Mon, 12 Dec 2016 13:12:00 -0000 [thread overview]
Message-ID: <274ea915-a628-04ff-d595-dc0301b41c29@linux.vnet.ibm.com> (raw)
In-Reply-To: <425c6518-69f7-e68d-9599-d81c8c137c96@redhat.com>
Hi Florian,
I've observed a new test-failure string/tst-strcoll-overflow after this
patch has been commited.
The test uses:
#define TIMEOUT 300
#define EXPECTED_SIGNAL SIGALRM
#define EXPECTED_STATUS 0
With the old test-skeleton, it either timed out or strcoll returned in
time and do_test returns 0. The test passes as WEXITSTATUS (status) ==
EXPECTED_STATUS.
With the new test-driver, the out-file contains:
0
Expected signal 'Alarm clock' from child, got none
If do_test would return e.g. 2 and EXPECTED_STATUS is defined to 2, the
test would pass. But if the testcase is then called with --direct, it
would return 2 instead of 0!
Shall the new test-driver be able to handle this case?
Bye
Stefan
next prev parent reply other threads:[~2016-12-12 13:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 20:30 Florian Weimer
2016-11-28 21:51 ` Florian Weimer
2016-11-28 22:58 ` Andreas Schwab
2016-11-29 7:52 ` Florian Weimer
2016-12-02 19:21 ` Carlos O'Donell
2016-12-05 15:57 ` Florian Weimer
2016-12-07 13:20 ` Florian Weimer
2016-12-08 14:29 ` Carlos O'Donell
2016-12-10 15:08 ` Andreas Schwab
2016-12-10 19:17 ` Florian Weimer
2016-12-10 19:39 ` Andreas Schwab
2016-12-12 10:00 ` Florian Weimer
2016-12-12 18:16 ` Andreas Schwab
2016-12-10 15:23 ` [PATCH] Fix testsuite timeout handling Andreas Schwab
2016-12-10 15:36 ` Florian Weimer
2016-11-28 23:11 ` [PATCH] support: Introduce new subdirectory for test infrastructure Joseph Myers
2016-11-29 6:41 ` Florian Weimer
2016-11-30 14:16 ` Carlos O'Donell
2016-12-12 13:12 ` Stefan Liebler [this message]
2016-12-12 14:50 ` Florian Weimer
2016-12-12 16:38 ` Stefan Liebler
2016-12-12 22:16 ` 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=274ea915-a628-04ff-d595-dc0301b41c29@linux.vnet.ibm.com \
--to=stli@linux.vnet.ibm.com \
--cc=libc-alpha@sourceware.org \
/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).