From: Joseph Myers <joseph@codesourcery.com>
To: Albert ARIBAUD <albert.aribaud@3adev.fr>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH v8 2/2] Y2038: make __tz_convert compatible with 64-bit-time
Date: Thu, 04 Oct 2018 15:05:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1810041445560.25558@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20181004163651.4d8362a4@athena>
On Thu, 4 Oct 2018, Albert ARIBAUD wrote:
> Could anyone explain to me why the summary PASS count and the actual
> PASS result file count disagree?
The rules for generating some files used in the testsuite generate the
.test-result files; those files are not listed in tests-special as being
tests, but some other similar files, using the same makefile rules, are so
listed, hence the files being generated. It's the settings of tests and
tests-special in each subdirectory that determine what counts as a test
for the purposes of the summaries.
(I think the files in question probably *should* be listed in
tests-special.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-10-04 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 7:31 [PATCH v8 1/2] Y2038: Add 64-bit time for all architectures Albert ARIBAUD (3ADEV)
2018-09-26 7:31 ` [PATCH v8 2/2] Y2038: make __tz_convert compatible with 64-bit-time Albert ARIBAUD (3ADEV)
2018-09-26 16:14 ` Joseph Myers
2018-09-29 11:41 ` Albert ARIBAUD
2018-09-30 13:38 ` Joseph Myers
2018-10-04 11:13 ` Albert ARIBAUD
2018-10-04 12:16 ` Joseph Myers
2018-10-04 14:36 ` Albert ARIBAUD
2018-10-04 14:48 ` Albert ARIBAUD
2018-10-04 15:05 ` Joseph Myers [this message]
2018-09-26 8:41 ` [PATCH v8 1/2] Y2038: Add 64-bit time for all architectures Florian Weimer
2018-09-26 14:39 ` Albert ARIBAUD
2018-09-26 14:43 ` Florian Weimer
2018-09-26 16:11 ` Joseph Myers
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=alpine.DEB.2.21.1810041445560.25558@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=albert.aribaud@3adev.fr \
--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).