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 v2] tiff: add ptest support
Date: Tue, 22 Sep 2026 11:12:17 +0200	[thread overview]
Message-ID: <DLLQ9LLMY585.1LEHNNH5I80QP@bootlin.com> (raw)
In-Reply-To: <20260921101102.2619364-1-HimaniRamesh.Barde@windriver.com>

Hi,

On Mon Sep 21, 2026 at 12:11 PM 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 list of C test programs is defined once in the recipe (TIFF_PTEST_PROGS)
> and substituted into run-ptest at install time to avoid duplication. The
> wrapper emits automake-style PASS/FAIL/SKIP results and skips two tests
> whose optional support is not built in the default configuration: the JBIG
> test (jbig is not in the default PACKAGECONFIG) and the thumbnail test (the
> thumbnail tool is not built).
>
> Registered in ptest-packagelists.inc under PTESTS_SLOW; the suite runs in
> roughly 30s on qemux86-64.
>
> Validated on qemux86-64: 17 C unit tests and 85 shell-script tests pass,
> 2 skipped (jbig, thumbnail), 0 failed.

This fails on different architectures on our test infra:

Failed ptests:
{'tiff': ['test_ifd_loop_detection']}

Full log: https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/9053625/raw_inline
Parent build: https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4607
Other archs:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/1249
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1234

Can you have a look?

Thanks,
Antonin


      reply	other threads:[~2026-09-22  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260915073518.2271284-1-HimaniRamesh.Barde@windriver.com>
2026-09-21 10:11 ` [PATCH v2] tiff: add ptest support Himani Ramesh Barde
2026-09-22  9:12   ` 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=DLLQ9LLMY585.1LEHNNH5I80QP@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