From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 778] Notify patch authors about CI failures by email
Date: Fri, 06 Aug 2021 06:28:02 +0000 [thread overview]
Message-ID: <bug-778-149-IdzXtu30R2@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-778-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=778
Lijuan Tu (lijuan.tu@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|FIXED |---
CC| |lijuan.tu@intel.com
--- Comment #2 from Lijuan Tu (lijuan.tu@intel.com) ---
(In reply to lingwei from comment #1)
> @Ali Alnubani
>
> This issue have been fixed, when patch build failed or smoke test failed,
> the report will send to the patch submitter directly.
Lingwei only fixed the issue in Intel CI, not dpdklab in unh.
Intel is making effort to align with community as much as possible.
Snice the request is to UNH, so reopen the ticket.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-08-06 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 10:53 bugzilla
2021-08-06 6:09 ` bugzilla
2021-08-06 6:28 ` bugzilla [this message]
2021-08-12 13:23 ` 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=bug-778-149-IdzXtu30R2@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).