test suite reviews and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Patrick Robb <probb@iol.unh.edu>, Manit Mahajan <mmahajan@iol.unh.edu>
Cc: dts@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v2] compress: resolve test failure from incomplete output capture
Date: Thu, 17 Jul 2025 10:40:16 +0200	[thread overview]
Message-ID: <CAJFAV8x_pe1h26p6LSisHBW7Y=31_++gr7G3y+xkkLwOx7BiDg@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUCMjvK-GabpdVyGgVa5P37THxhD9vsOpBUvisi3o2qdLg@mail.gmail.com>

Hello,

On Wed, Jul 16, 2025 at 10:36 PM Patrick Robb <probb@iol.unh.edu> wrote:
>
> On Wed, Jul 16, 2025 at 3:24 PM Manit Mahajan <mmahajan@iol.unh.edu> wrote:
>>
>> The compress unit test uses send_expect() with '>' to determine
>> when the command completed. A recent patch introduced a
>> deprecation warning for coremask, which includes a '>' in the
>> output. This causes send_expect() to exit early,
>> resulting in missed test output, leading to false failures.
>>
>> This is fixed by changing the expected termination prompt from
>> '>' to 'RTE>'. This change address issues from the v1 patch,
>> which incorrectly modified the EAL option from coremask to
>> corelist.
>>
>> Signed-off-by: Manit Mahajan <mmahajan@iol.unh.edu>
>
> Thanks. So, if we change the expect string to "RTE>", the warning will not trigger the expect and unit tests will complete before the execution proceeds? Sounds good.

On the principle, that sounds good to me too.

Just a note that other parts of "old" dts may be affected:
$ git grep 'send_expect.*">"'
tests/TestSuite_ieee1588.py:        self.dut.send_expect("start", ">", 10)
tests/TestSuite_multiprocess.py:
self.session_secondary.send_expect("send hello_primary", ">")
tests/TestSuite_multiprocess.py:
self.session_secondary.send_expect("send hello_secondary", ">")
tests/TestSuite_multiprocess.py:            self.dut.send_expect("send
%s" % line, ">")
tests/TestSuite_multiprocess.py:
self.session_secondary.send_expect("send hello_primary", ">")
tests/TestSuite_multiprocess.py:
self.session_secondary.send_expect("send hello_secondary", ">", 100)
tests/TestSuite_multiprocess_iavf.py:
self.session_secondary.send_expect("send hello_primary", ">")
tests/TestSuite_multiprocess_iavf.py:
self.session_secondary.send_expect("send hello_secondary", ">")
tests/TestSuite_multiprocess_iavf.py:
self.dut.send_expect("send %s" % line, ">")
tests/TestSuite_multiprocess_iavf.py:
self.session_secondary.send_expect("send hello_primary", ">")
tests/TestSuite_multiprocess_iavf.py:
self.session_secondary.send_expect("send hello_secondary", ">", 100)
tests/TestSuite_shutdown_api.py:            self.dut.send_expect("set
link-up port %d" % i, ">")
tests/TestSuite_speed_capabilities.py:
self.dut.send_expect("set link-up port %d" % i, ">")
tests/compress_common.py:    test_case.dut.send_expect(cmdline, ">", 30)
tests/compress_common.py:    out =
test_case.dut.send_expect("compressdev_autotest", ">", 30)


How do we proceed now?
Do you want me to push this fix in the dts legacy repo?


-- 
David Marchand


  reply	other threads:[~2025-07-17  8:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 20:30 [PATCH] tests/compress_common: replace coremask with corelist in compress_common Manit Mahajan
2025-07-11 21:30 ` Patrick Robb
2025-07-15  7:42   ` David Marchand
2025-07-16 15:53     ` Manit Mahajan
2025-07-16 19:24 ` [PATCH v2] compress: resolve test failure from incomplete output capture Manit Mahajan
2025-07-16 20:30   ` Patrick Robb
2025-07-17  8:40     ` David Marchand [this message]
2025-07-17 18:33       ` Patrick Robb
2025-07-16 15:28 Manit Mahajan
2025-07-16 15:43 ` Manit Mahajan

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='CAJFAV8x_pe1h26p6LSisHBW7Y=31_++gr7G3y+xkkLwOx7BiDg@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dts@dpdk.org \
    --cc=mmahajan@iol.unh.edu \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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 NNTP newsgroup(s).