From: Thomas Monjalon <thomas@monjalon.net>
To: ci@dpdk.org
Cc: j.hendergart@f5.com, Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: [dpdk-ci] CI reliability
Date: Sun, 24 May 2020 11:50:43 +0200 [thread overview]
Message-ID: <5232496.1u8oYCttyy@thomas> (raw)
Hi all,
I think we have a CI reliability issue in general.
Perhaps we lack some alert mechanism warning test platform maintainers
when too many tests are failing.
Recent example: the community lab compilation test is failing on
Fedora 31 for at least 2 weeks, and I don't see any action to fix it:
https://lab.dpdk.org/results/dashboard/patchsets/11040/
Because of such recurring errors, the whole CI becomes irrelevant.
Please, we need taking actions to avoid such issue in the near future.
next reply other threads:[~2020-05-24 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 9:50 Thomas Monjalon [this message]
2020-05-26 20:27 ` Lincoln Lavoie
2020-05-26 21:10 ` Thomas Monjalon
2021-06-02 7:27 Thomas Monjalon
2021-06-02 12:55 ` Lincoln Lavoie
2021-06-02 13:34 ` Thomas Monjalon
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=5232496.1u8oYCttyy@thomas \
--to=thomas@monjalon.net \
--cc=ci@dpdk.org \
--cc=j.hendergart@f5.com \
--cc=lylavoie@iol.unh.edu \
/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).