From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: ci@dpdk.org, James Hendergart <j.hendergart@f5.com>,
Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
Subject: Re: [dpdk-ci] community lab at UNH is unreachable
Date: Mon, 16 Nov 2020 08:41:07 -0500 [thread overview]
Message-ID: <CAOE1vsO7emmc_UfjCnRPAmUGsEe++x0Uj3SwHByo6NrNKGfmOg@mail.gmail.com> (raw)
In-Reply-To: <6448213.hl59zpk5d8@thomas>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
Thomas,
This issue has nothing to do with the DPDK lab. The UNH-IOL's primary
firewall router failed Saturday evening and we had to cut over to a backup
while repair parts are being flown in (should be here by end of day). I'm
working on fixing the website, which is the only issue with the DPDK lab,
the testing itself is still all running, with reports being delivered to
patchworks.
I'm sorry for the bad timing of this failure, but it is unrelated to to the
DPDK project itself.
Cheers,
Lincoln
On Mon, Nov 16, 2020 at 5:36 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> Hi,
>
> There is a problem to access to the CI results:
> https://lab.dpdk.org/results/dashboard
> It is failing with timeout.
>
> Note we had other reliability issues in the past weeks.
> The reliability of the CI should be the first priority,
> it is the key, otherwise CI is meaningless.
>
>
>
--
*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)
<https://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 2586 bytes --]
next prev parent reply other threads:[~2020-11-16 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 10:36 Thomas Monjalon
2020-11-16 13:41 ` Lincoln Lavoie [this message]
2020-11-16 15:35 ` Lincoln Lavoie
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=CAOE1vsO7emmc_UfjCnRPAmUGsEe++x0Uj3SwHByo6NrNKGfmOg@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=j.hendergart@f5.com \
--cc=tdelanerolle@linuxfoundation.org \
--cc=thomas@monjalon.net \
/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).