From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 168] Record pipeline CI issues
Date: Wed, 13 Mar 2019 18:41:11 +0000 [thread overview]
Message-ID: <bug-168-149-i9aHpGvfyN@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-168-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=168
Jeremy Plsek (jplsek@iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Jeremy Plsek (jplsek@iol.unh.edu) ---
We now submit a test result with no test runs when this happens. For logged in
users, they can download any artifacts that were created before the test
crashed. See the link above as an example.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-03-13 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 15:46 bugzilla
2019-03-12 16:31 ` bugzilla
2019-03-13 18:41 ` 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-168-149-i9aHpGvfyN@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).