From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 431] Missing performance results in Patchwork checks, and possible false positives
Date: Wed, 22 Apr 2020 16:34:16 +0000 [thread overview]
Message-ID: <bug-431-149-4FGhPx6sus@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-431-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=431
Brandon Lo (blo@iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--- Comment #5 from Brandon Lo (blo@iol.unh.edu) ---
Fixed.
This issue is due to concurrent running tests.
Our internal testing job would run a job to send a performance report email to
vendors for a given patch. The problem is that this email would be sent after
all of a given vendor's machines are done testing (vendor A), but it could
occur before all of the machines of another vendor finishes (vendor B).
This results in all of the results from the first vendor (A) being sent, but
the internal script will pick up the existing results created by the unfinished
vendor B and send those out as well.
This can be seen with email timings. An unfinished Mellanox report email could
have one single testbed's result in the email, and it will always be sent at
the same time as another vendor's email (Intel for example).
The fix was to add support for sending a specific vendor's email only when all
of the given vendor's testbeds are finished testing.
We have tested this by using dry runs of the email sending script with
successful separation of vendor testbed results.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2020-04-22 16:34 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
2020-04-22 16:34 ` bugzilla [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=bug-431-149-4FGhPx6sus@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).