From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 172] Send updated reports after a rerun
Date: Tue, 19 Mar 2019 17:44:48 +0000 [thread overview]
Message-ID: <bug-172-149-s0KudfEnvo@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-172-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=172
Jeremy Plsek (jplsek@iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jeremy Plsek (jplsek@iol.unh.edu) ---
We now send updated reports after a rerun.
Example:
https://lab.dpdk.org/results/dashboard/patchsets/4892/#env-10
https://patches.dpdk.org/patch/51233/
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-03-19 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 15:52 bugzilla
2019-03-19 17:44 ` 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-172-149-s0KudfEnvo@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).