Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <HimaniRamesh.Barde@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Cc: "Randy MacLeod" <Randy.MacLeod@windriver.com>,
	"Shiva Komati" <Shiva.Komati@windriver.com>
Subject: Re: [OE-core] [PATCH] tiff: add ptest support
Date: Wed, 16 Sep 2026 08:36:42 +0200	[thread overview]
Message-ID: <DLGJ77DHTM2P.IQVGF1XGUBW1@bootlin.com> (raw)
In-Reply-To: <20260915073620.2271352-1-HimaniRamesh.Barde@windriver.com>

Hi,

On Tue Sep 15, 2026 at 9:36 AM CEST, Himani Ramesh Barde via lists.openembedded.org wrote:
> Enable ptest for tiff (libtiff), running the upstream test suite shipped
> in the source test/ directory: the C unit-test programs (check_PROGRAMS)
> plus the shell-script tests that exercise the tiff command-line tools.
>
> do_compile_ptest builds the test programs via "make check TESTS=" (build
> only, no run). do_install_ptest installs the compiled test binaries (real
> ELF from test/.libs, static testtypes from test/), the shell test scripts,
> the shared common.sh helper, and the images/refs data. common.sh is
> adjusted so the scripts find the installed tiff tools in ${bindir} rather
> than the build tree's ../tools, and run-ptest recreates the SOURCE_DIR
> path that test_ifd_loop_detection was compiled with so its images resolve
> on target.
>
> The run-ptest wrapper emits automake-style PASS/FAIL/SKIP results and
> skips the JBIG test (JBIG is not in the default PACKAGECONFIG) and the
> thumbnail test (the thumbnail tool is not built by default).
>
> The recipe is registered in ptest-packagelists.inc (PTESTS_SLOW), and
> buildpaths QA is skipped for the -ptest package since the compiled test
> binaries legitimately embed build paths.
>
> Validated on qemux86-64: all C tests and shell tests pass, 2 skipped
> (jbig, thumbnail), 0 failed.

This fails on:

- riscv64: https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2415
- arm64: https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4537
- x86-64: https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4564
- musl: https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/1209
        https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1192

Can you have a look?

Thanks,
Antonin


      parent reply	other threads:[~2026-09-16  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  7:36 [PATCH] tiff: add ptest support Himani Ramesh Barde
2026-09-15 21:19 ` Randy MacLeod
2026-09-15 21:23   ` [OE-core] " Richard Purdie
2026-09-16  6:36 ` Antonin Godard [this message]

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=DLGJ77DHTM2P.IQVGF1XGUBW1@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=HimaniRamesh.Barde@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Shiva.Komati@windriver.com \
    --cc=openembedded-core@lists.openembedded.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