From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 511] Add check if performance tests are needed
Date: Mon, 20 Jul 2020 13:17:11 +0000 [thread overview]
Message-ID: <bug-511-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=511
Bug ID: 511
Summary: Add check if performance tests are needed
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: Intel Lab
Assignee: ci@dpdk.org
Reporter: kevuzaj@gmail.com
Target Milestone: ---
I submitted a patch for DPDK Unit Test [1], that only changed one file in
app/test/.
I noticed that UNH is running performance testing on these patches, when really
it is not required. It may also run performance testing when there is a change
to a .rst only etc.
Sometimes it may be difficult to know if something will impact performance, but
for these very obvious cases at least maybe some rule could be added so that
performance testing is not run.
Of course, it is not an issue in receiving the mails with the results, but
perhaps it would free up some lab resources, hence the suggestion.
[1]
http://patchwork.dpdk.org/patch/74486/
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-07-20 13:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-511-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).