From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdklab <dpdklab@iol.unh.edu>,
ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-ci] No job running in UNH lab
Date: Mon, 4 Oct 2021 14:55:04 -0400 [thread overview]
Message-ID: <CAOE1vsOe_-wg0wWKLfyXrV=Df1OjuBU7LA61aNX3eHhZM_UANw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ynv+wTgTTFOWSJfpy0-DMqqbMZ4vBbb6hu9TghgOqZRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
Hello David,
Apologizes for the slow email reply. Last week we had a Jenkins update
fail, which took down the automated testing and took some time to get
rolled back and restored. This should be back up and running more smoothly
now and will be catching up on the backlog over the next few days.
Please let us know if there is anything else you notice looking wrong.
Cheers,
Lincoln
On Fri, Oct 1, 2021 at 4:29 AM David Marchand <david.marchand@redhat.com>
wrote:
> On Fri, Oct 1, 2021 at 10:25 AM David Marchand
> <david.marchand@redhat.com> wrote:
> >
> > Hello guys,
> >
> > Trying to merge patches, I went to look at the UNH dashboard since I
> > was missing test reports.
> > We have a rather long backlog of pending jobs (going back to 09/24).
> >
> > But the CI job queue is empty.
> > https://lab.dpdk.org/results/dashboard/status/
> >
> >
> > Can we get this fixed quickly?
>
> I bcc: people instead of regular cc:...
> Sorry, fixed.
>
>
> --
> David Marchand
>
>
--
*Lincoln Lavoie*
Principal 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: 2820 bytes --]
prev parent reply other threads:[~2021-10-04 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 8:25 David Marchand
2021-10-01 8:29 ` David Marchand
2021-10-04 18:55 ` Lincoln Lavoie [this message]
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='CAOE1vsOe_-wg0wWKLfyXrV=Df1OjuBU7LA61aNX3eHhZM_UANw@mail.gmail.com' \
--to=lylavoie@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dpdklab@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--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).