From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: RE: Failing PER_PATCH_BUILD reports can be too large
Date: Sat, 8 Oct 2022 01:25:38 +0000 [thread overview]
Message-ID: <CY5PR11MB61877E92812115DE679CDABDF55E9@CY5PR11MB6187.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM4PR12MB516784045BD59102382880BFDA5A9@DM4PR12MB5167.namprd12.prod.outlook.com>
I will think about it, thanks.
> -----Original Message-----
> From: Ali Alnubani <alialnu@nvidia.com>
> Sent: Tuesday, October 4, 2022 7:50 PM
> To: Tu, Lijuan <lijuan.tu@intel.com>
> Cc: ci@dpdk.org
> Subject: Failing PER_PATCH_BUILD reports can be too large
>
> Hi Lijuan,
>
> I noticed that some of the failing PER_PATCH_BUILD reports sys_stv@intel.com
> sends to the test-report mailing list are larger than the limit of 500KB, causing
> them to bounce back. Most recent example:
> Subject: [dpdk-test-report] |FAILURE| pw(117114) sid(24904)
> job(PER_PATCH_BUILD4461)[v2,3/3] net/cnxk: support congestion management
> ops
>
> Can the size of these reports be reduced? Maybe by only including the build
> errors? (Might be difficult because ninja doesn't redirect build errors to stderr
> separately)
>
> Thanks,
> Ali
prev parent reply other threads:[~2022-10-08 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 11:49 Ali Alnubani
2022-10-08 1:25 ` Tu, Lijuan [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=CY5PR11MB61877E92812115DE679CDABDF55E9@CY5PR11MB6187.namprd11.prod.outlook.com \
--to=lijuan.tu@intel.com \
--cc=alialnu@nvidia.com \
--cc=ci@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).