DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Manit Mahajan <mmahajan@iol.unh.edu>, ci@dpdk.org
Cc: alialnu@nvidia.com, shaibran@amazon.com
Subject: Re: Test Report Email Too Large
Date: Fri, 20 Jun 2025 13:30:24 -0400	[thread overview]
Message-ID: <CAJvnSUDc9LTMH7GRA2LgXicY3v_QpBR4_3JNfW8HENWDSpqHag@mail.gmail.com> (raw)
In-Reply-To: <CANcZauytxFfCza=_mUzXgVqBecCd64hXbeP=Xq1=SbfMQ8eo5w@mail.gmail.com>

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

+ci@dpdk.org <ci@dpdk.org>

On Fri, Jun 20, 2025 at 1:14 PM Manit Mahajan <mmahajan@iol.unh.edu> wrote:

> Hi Ali and Shai,
>
> I'm reaching out regarding a test report that was flagged as too large for
> the mailing list:
> |FAILURE| pw154549 [PATCH] crypto/cnxk: add sessionless asym cn20k support
>
> The rejection message indicated that the email was 564KB, exceeding the
> 500KB limit:
> Message body is too big: 564556 bytes with a limit of 500 KB
>
> However, when looking at the test report, the actual email size appears to
> be well within the limit. The test report emails says it is 17KB. Here is
> the link to the report:
>
> http://inbox.dpdk.org/test-report/505157275.540.1750274462804@ip-10-159-234-77.eu-west-1.compute.internal/
>
> The test was run on al-sw-devops. Flagging this so it doesn’t go unnoticed
> and to help prevent future occurrences.
>
> Best Regards,
> Manit Mahajan
> InterOperability Laboratory
>

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

           reply	other threads:[~2025-06-20 17:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CANcZauytxFfCza=_mUzXgVqBecCd64hXbeP=Xq1=SbfMQ8eo5w@mail.gmail.com>]

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=CAJvnSUDc9LTMH7GRA2LgXicY3v_QpBR4_3JNfW8HENWDSpqHag@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=mmahajan@iol.unh.edu \
    --cc=shaibran@amazon.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;
as well as URLs for NNTP newsgroup(s).