From: Lukasz Majewski <lukma@denx.de>
To: libc-alpha <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>, libc-help@sourceware.org
Subject: Question regarding test suite build
Date: Wed, 21 Jul 2021 15:35:22 +0200 [thread overview]
Message-ID: <20210721153522.31ac5aca@ktm> (raw)
[-- Attachment #1: Type: text/plain, Size: 2166 bytes --]
Dear Community,
I've thought about using yocto's ptest utility to check correctness of
glibc on for example ARMv7 or i386.
The idea would be simple - copy cross compiled tests - e.g
test-clock_settime to the target's rootfs when created in yocto.
Then, after booting up the board (in for example qemu) run those tests
with ptest-runner.
Advantages of this approach:
1. DO NOT use SSH and test-wrapper script to copy those binaries
2. Tests would be cross compiled on powerfull HOST machine
3. Run tests on target device - can be qemu or custom board (which
would help a lot with validation)
The problem I'm facing now is that make check does everything at once (
it cross compiles tests, executes them and prints results).
I would probably need to add new make rule (like make tst or such)
The first step would be just cross compile tests. The
'host-built-program-cmd' from Makeconfig seems to be responsible for it.
Questions:
----------
1. I'm adjusting Rules and then execute:
rm ./time/tst-clock_settime*
make V=1 --debug=b PARALLELMFLAGS="-j8" subdirs=time check
but the changes from Rules or Makeconfig are not applied (at least not
in logs).
For example I've added to Rules (line 297)
$(objpfx)%.out:·%.input·$(objpfx)%
@echo·FOO$
@echo·$(make-test-out)·>·$@·<·$(word·1,$^);
to see how tests are built, but no output is visible.
2. What is the purpose of 'all-testsuite' variable in Makerules (line
1255)?
Is a separate (helper) library (libtestsuite) built to have all eligible
tests in it?
3. It looks like some env variables GCONV_PATH and LOCPATH are set when
tests are built (Makeconfig line 745) in run-program-env.
I'm wondering how I could avoid setting it on target (store in bash.rc
when image is created?) and just call the test itself (like
tst-clock_settime)?
Thanks in advance for help.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-07-21 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 13:35 Lukasz Majewski [this message]
2021-07-27 20:34 ` Question regarding test suite build 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210721153522.31ac5aca@ktm \
--to=lukma@denx.de \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-help@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).