DPDK CI discussions
 help / color / mirror / Atom feed
* Failing PER_PATCH_BUILD reports can be too large
@ 2022-10-04 11:49 Ali Alnubani
  2022-10-08  1:25 ` Tu, Lijuan
  0 siblings, 1 reply; 2+ messages in thread
From: Ali Alnubani @ 2022-10-04 11:49 UTC (permalink / raw)
  To: Tu, Lijuan; +Cc: ci

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-10-08  1:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-04 11:49 Failing PER_PATCH_BUILD reports can be too large Ali Alnubani
2022-10-08  1:25 ` Tu, Lijuan

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).