From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: dev@dpdk.org
Subject: [dpdk-dev] Pausing failing tests
Date: Thu, 19 Nov 2020 16:17:34 -0500 [thread overview]
Message-ID: <CAOE1vsO8yyDcd6kpVf5b7YVux-uEUbSWwhU1v_FgxCRGCd+fDA@mail.gmail.com> (raw)
Hello All,
The CI group discussed an issue that has recently come up, where some
tests are failing for a well known cause. The conclusion was, in
cases where the failure is well known or a patch is already in process
(i.e. in DPDK or a downstream project like SPDK), a DPDK maintainer
can submit a request (via bugzilla) to remove the failing test from
operation. The CI labs will act on the ticket and then re-assign it
to the maintainer. It is the maintainer's responsibility to then
alert the CI labs when the bug / failure is fixed and the test should
be re-enabled. The bugzilla ticket must remain open until the test is
re-enabled.
Community CI Minutes:
https://mails.dpdk.org/archives/ci/2020-November/000894.html
Example Bugzilla Ticket: https://bugs.dpdk.org/show_bug.cgi?id=579
Cheers,
Lincoln
--
Lincoln Lavoie
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
reply other threads:[~2020-11-19 21:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAOE1vsO8yyDcd6kpVf5b7YVux-uEUbSWwhU1v_FgxCRGCd+fDA@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=dev@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).