From: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
To: Brandon Lo <blo@iol.unh.edu>
Cc: David Marchand <david.marchand@redhat.com>,
dpdklab <dpdklab@iol.unh.edu>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
ci@dpdk.org
Subject: Re: [dpdk-ci] No more reports from UNH since series 10524
Date: Mon, 22 Jun 2020 13:46:51 -0400 [thread overview]
Message-ID: <CAFXL6f9qTFMA0BuZT5UJYDmPNHZ1Khg6vk+OPPHnubg_vXLKxg@mail.gmail.com> (raw)
In-Reply-To: <CAOeXdvZz1Rtq9JHrB=-AohMb5Kes=UP-dskbSi9bfk5twQbCDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
Hi Brandon,
Do you have an alert/notification and escalation path for outages like
this.
Trishan
On Mon, Jun 22, 2020 at 12:58 PM Brandon Lo <blo@iol.unh.edu> wrote:
> Hi David,
>
> It appears that the Jenkins CI broke overnight during the weekend.
> I have taken this time to update the CI and fix a few problems.
>
> It should be back up now.
>
> Thanks,
> Brandon
>
> On Mon, Jun 22, 2020 at 9:46 AM David Marchand <david.marchand@redhat.com>
> wrote:
>
>> Looking at the UNH dashboard, I can't see any recent series after one
>> of mine that dates Friday 19th.
>> Is there something broken?
>>
>> Thanks.
>>
>>
>> --
>> David Marchand
>>
>>
>
> --
>
> Brandon Lo
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
>
> blo@iol.unh.edu
>
> www.iol.unh.edu
>
--
Trishan R. de Lanerolle
Technical Program Manager & Community Architect
Networking, Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle
email: tdelanerolle@linuxfoundation.org
[-- Attachment #2: Type: text/html, Size: 3844 bytes --]
next prev parent reply other threads:[~2020-06-22 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 13:46 David Marchand
2020-06-22 16:58 ` Brandon Lo
2020-06-22 17:46 ` Trishan de Lanerolle [this message]
2020-06-22 19:26 ` 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=CAFXL6f9qTFMA0BuZT5UJYDmPNHZ1Khg6vk+OPPHnubg_vXLKxg@mail.gmail.com \
--to=tdelanerolle@linuxfoundation.org \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dpdklab@iol.unh.edu \
--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).