From: Ali Alnubani <alialnu@mellanox.com>
To: Brandon Lo <blo@iol.unh.edu>,
"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>
Cc: "bugzilla@dpdk.org" <bugzilla@dpdk.org>,
"ci@dpdk.org" <ci@dpdk.org>,
Thomas Monjalon <thomasm@mellanox.com>,
David Marchand <david.marchand@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Ye, Xiaolong" <xiaolong.ye@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Raslan Darawsheh <rasland@mellanox.com>
Subject: Re: [dpdk-ci] [Bug 431] Missing performance results in Patchwork checks, and possible false positives
Date: Sun, 19 Apr 2020 13:31:57 +0000 [thread overview]
Message-ID: <AM0PR05MB440157B5ECC5753020F9C386D7D70@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <bug-431-149@http.bugs.dpdk.org/>
Hello,
> -----Original Message-----
> From: ci <ci-bounces@dpdk.org> On Behalf Of bugzilla@dpdk.org
> Sent: Tuesday, March 31, 2020 5:43 PM
> To: ci@dpdk.org
> Subject: [dpdk-ci] [Bug 431] Missing performance results in Patchwork checks,
> and possible false positives
>
Patchwork is reporting a false positive on patch https://patches.dpdk.org/patch/68908/ (at least) for iol-mellanox-Performance because of this.
Two reports were sent by the lab for this patch in the following order:
https://mails.dpdk.org/archives/test-report/2020-April/127163.html (Failing, Sun Apr 19 13:57:32 CEST 2020).
http://mails.dpdk.org/archives/test-report/2020-April/127165.html (Passing, Sun Apr 19 14:06:51 CEST 2020).
And even though one of the reports is failing, the current status says passing on Patchwork.
What's the reason why aren't all the performance test results for a vendor sent in the same report?
Thanks,
Ali
next prev parent reply other threads:[~2020-04-19 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 14:42 bugzilla
2020-04-19 13:31 ` Ali Alnubani [this message]
2020-04-22 16:34 ` bugzilla
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=AM0PR05MB440157B5ECC5753020F9C386D7D70@AM0PR05MB4401.eurprd05.prod.outlook.com \
--to=alialnu@mellanox.com \
--cc=blo@iol.unh.edu \
--cc=bugzilla@dpdk.org \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dpdklab@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=rasland@mellanox.com \
--cc=thomasm@mellanox.com \
--cc=xiaolong.ye@intel.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).