test suite reviews and discussions
 help / color / mirror / Atom feed
From: Manit Mahajan <mmahajan@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Patrick Robb <probb@iol.unh.edu>,
	dts@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] tests/compress_common: replace coremask with corelist in compress_common
Date: Wed, 16 Jul 2025 11:53:18 -0400	[thread overview]
Message-ID: <CANcZauyk3RbgT467Das=vdpwWh+6mh_6WZqqSSLt2==H3t5OJQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xM12ZxFSsrRa3Ve=momUN64m+knTnqOwtfmXugqNzaYw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]

Hi,

Thanks for the clarification. I had misunderstood the patch that added the
coremask warning and incorrectly assumed that -c was deprecated. Upon
closer review, I see that the patch only adds warning logs when using
coremask but does not deprecate the -c option. The actual problem is that
the warning message includes a '>', which causes send_expect('>') to return
prematurely and miss important test output. I will address this in v2 by
changing the expected prompt to 'RTE>'.


On Tue, Jul 15, 2025 at 3:42 AM David Marchand <david.marchand@redhat.com>
wrote:

> Hello,
>
> On Fri, Jul 11, 2025 at 11:36 PM Patrick Robb <probb@iol.unh.edu> wrote:
> >
> > This seems fine in principle.
> >
> > Did you ever figure out why the compressdev_autotest was failing with
> coremask used in the first place? I haven't looked at the coremask
> deprecation patch that you had found, but David said on slack that it
> didn't remove the option to use the coremask EAL arg, it just discourages
> it with a warning.
> >
> > On Fri, Jul 11, 2025 at 4:32 PM Manit Mahajan <mmahajan@iol.unh.edu>
> wrote:
> >>
> >> The compress_common.py script previously used the --coremask parameter,
> >> which has been removed from DPDK. As a result, zlib_pmd test cases
> >> fail when invoking this script. This patch updates the script to
>
> There is no --coremask EAL option.
> And the option -c was not removed.
>
> Please refine the rca.
>
> >> use the --corelist parameter instead, which is the more common
> >> way to specify core assignment in DPDK.
>
> There is no --corelist EAL option.
>
> Only -c, -l and --lcores exist atm.
>
>
> --
> David Marchand
>
>

[-- Attachment #2: Type: text/html, Size: 2286 bytes --]

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 20:30 Manit Mahajan
2025-07-11 21:30 ` Patrick Robb
2025-07-15  7:42   ` David Marchand
2025-07-16 15:53     ` Manit Mahajan [this message]
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
2025-07-17 18:33       ` Patrick Robb

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='CANcZauyk3RbgT467Das=vdpwWh+6mh_6WZqqSSLt2==H3t5OJQ@mail.gmail.com' \
    --to=mmahajan@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dts@dpdk.org \
    --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).