From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: "requires 32-and-64" tests enabled when 64-bit; -arch {32,64} behavior changed
Date: Wed, 02 Jan 2008 16:48:00 -0000 [thread overview]
Message-ID: <477BBEBC.909@redhat.com> (raw)
Just a heads up.
The test framework as been extended to better support two 32/64 bit cases:
"32-and-64":
This is the case where a 64-bit funit test-case is explicitly testing
interactions involving both 32-bit and 64-bit test programs. For
instance, the sequence of 64-bit program execs 32-bit program execs
64-bit program.
Such tests use Config.getPkgLib32File and Config.getPkgLib64File (see
frysk.testbed.ExecCommand) to get 32-bit or 64-bit variants of a test
program.
The new guard missing32and64() is available to confirm that the test is
possible (for instance, a 32-bit funit does not support and hence should
skip such a test).
"32-on-64":
This the case where a 64-bit funit test-case is (unknowingly) being
tested against a 32-bit test programs.
Such tests use Config.getPkgLibFile() (which returns the applicable
32-bit or 64-bit program).
The new guard unresolvedOn32On64(BUG) is available for tests that work
when pure 32-on-32 and 64-on-64 but have problems when 32-on-64.
In addition, funit (TestRunner) has been modified so that it defaults to
running combined 32-and-64 tests (previously it skipped them); the
<<-arch 32>> and <<-arch 64>> options can be used to override this. For
instance, on a 64-bit system which does not have 32-bit test programs
installed <<funit -arch 64>> should be specified and will cause
"32-and-64" tests to be skipped.
Andrew
reply other threads:[~2008-01-02 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=477BBEBC.909@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@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).