public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Crystal Wood <crwood@redhat.com>
To: John Kacur <jkacur@redhat.com>, Tomas Glozar <tglozar@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
	Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH] rteval: Introduce E2E tests with output checking
Date: Thu, 18 Sep 2025 14:24:56 -0500	[thread overview]
Message-ID: <f0ed388cbd078cfe9a90366f2a3d40d18e113df4.camel@redhat.com> (raw)
In-Reply-To: <6f2a6564-ecf0-e77e-2ccf-5250eddab97f@redhat.com>

On Thu, 2025-09-18 at 13:56 -0400, John Kacur wrote:

> Test Summary Report
> -------------------
> e2e-tests/loads.t      (Wstat: 0 Tests: 8 Failed: 1)
>   Failed test:  5
> e2e-tests/measurement.t (Wstat: 0 Tests: 19 Failed: 6)
>   Failed tests:  13-14, 16-19
> Files=3, Tests=33, 308 wallclock secs ( 0.06 usr  0.00 sys + 146.20 cusr 
> 281.79 csys = 428.05 CPU)
> Result: FAIL
> make: *** [Makefile:22: check] Error 1
> 
> How do I identify which test is test number 5?
> Am I failing tests because of performance reasons or because the tests 
> expect an environment different from mine?

Passing -v to prove does this; not sure why we aren't using it in make
check.

-Crystal


  reply	other threads:[~2025-09-18 19:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  9:02 [PATCH] rteval: Introduce E2E tests with output checking Tomas Glozar
2025-09-18 17:56 ` John Kacur
2025-09-18 19:24   ` Crystal Wood [this message]
2025-09-26 11:12   ` Tomas Glozar
2025-11-04 12:57   ` Tomas Glozar
2025-09-18 19:22 ` Crystal Wood
2025-09-26 11:09   ` Tomas Glozar
2025-09-30 22:57     ` Crystal Wood

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=f0ed388cbd078cfe9a90366f2a3d40d18e113df4.camel@redhat.com \
    --to=crwood@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglozar@redhat.com \
    --cc=williams@redhat.com \
    /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