DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdklab <dpdklab@iol.unh.edu>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>,
	ci@dpdk.org,  Aaron Conole <aconole@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-ci] [dpdklab] No test report since 09/21
Date: Mon, 23 Aug 2021 10:38:01 -0400	[thread overview]
Message-ID: <CAOeXdvbxkD7je9A89hL2T_1poBM13j4Qyp34Y_d4tDckzKvQig@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8wOkn+fxXPJrP4bmvNdg9eCbk5XAbeMKUep7ouf1e4CBw@mail.gmail.com>

On Mon, Aug 23, 2021 at 8:37 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> Hello,
>
> Looking at the UNH web dashboard, it looks like we have no test since Friday.
>
> The CI status page shows "stuck" (?) jobs:
> Update Patchwork Status Build #27,492 is already in progress (ETA: N/A)
> Get-Patch-Sets Build #87,160 is already in progress (ETA: N/A)
>
>
> Could you double check?
>
> Thanks.
>
> --
> David Marchand

Hi David,

Thanks for letting us know. We restarted the frozen build in Jenkins.

We investigated this issue, and it looks like Jenkins froze as it
tried to run its temporary shell script during the job.
There is no clear cause for this issue, so for now the pipeline will
just forcibly restart any run that takes too long.

Thanks,
Brandon

-- 
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu

      reply	other threads:[~2021-08-23 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 12:37 [dpdk-ci] " David Marchand
2021-08-23 14:38 ` Brandon Lo [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=CAOeXdvbxkD7je9A89hL2T_1poBM13j4Qyp34Y_d4tDckzKvQig@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=lylavoie@iol.unh.edu \
    --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).