Failing PER_PATCH_BUILD reports can be too large

[Tu, Lijuan]

I will think about it, thanks.

> -----Original Message-----
> From: Ali Alnubani <alialnu at nvidia.com>
> Sent: Tuesday, October 4, 2022 7:50 PM
> To: Tu, Lijuan <lijuan.tu at intel.com>
> Cc: ci at 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 at 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