DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: david.marchand@redhat.com
Subject: Re: [PATCH 0/2] fix hash unit test for CI
Date: Fri, 31 Oct 2025 12:12:38 +0100	[thread overview]
Message-ID: <7529890.gtipl9YmvM@thomas> (raw)
In-Reply-To: <20251030175329.4041960-1-thomas@monjalon.net>

30/10/2025 18:50, Thomas Monjalon:
> When running the CI tests in GHA with UBSan enabled,
> for an unknown reason, a test is regularly going to timeout.
> While reducing the time needed for this test,
> a fix is added to fail nicely when there is not enough memory.
> 
> Thomas Monjalon (2):
>   test/hash: check memory allocation
>   test/hash: reduce time of functional R/W test

Applied quickly to fix CI tests.




      parent reply	other threads:[~2025-10-31 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 17:50 Thomas Monjalon
2025-10-30 17:50 ` [PATCH 1/2] test/hash: check memory allocation Thomas Monjalon
2025-10-31  7:51   ` David Marchand
2025-10-30 17:50 ` [PATCH 2/2] test/hash: reduce time of functional R/W test Thomas Monjalon
2025-10-31  8:18   ` David Marchand
2025-10-31 11:12 ` Thomas Monjalon [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=7529890.gtipl9YmvM@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).