From: David Marchand <david.marchand@redhat.com>
To: dpdklab@iol.unh.edu
Cc: ci@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: Re: [dpdk-ci] [Bug 495] make builds are getting stuck
Date: Mon, 13 Jul 2020 10:34:02 +0200 [thread overview]
Message-ID: <CAJFAV8x35MRrua5JWThXzvgMAPWo1hU0Wz_zqPph+tjsHzuCUg@mail.gmail.com> (raw)
In-Reply-To: <bug-495-149@http.bugs.dpdk.org/>
Guys,
On Tue, Jun 30, 2020 at 9:52 AM <bugzilla@dpdk.org> wrote:
>
> https://bugs.dpdk.org/show_bug.cgi?id=495
>
> Bug ID: 495
> Summary: make builds are getting stuck
> Product: lab
> Version: unspecified
> Hardware: All
> OS: All
> Status: UNCONFIRMED
> Severity: critical
> Priority: Normal
> Component: job scripts
> Assignee: ci@dpdk.org
> Reporter: alialnu@mellanox.com
> CC: dpdklab@iol.unh.edu
> Target Milestone: ---
>
> Need to pass 'MAKE_PAUSE=n' to 'make' builds in all CI checks (performance and
> compilation) because of the following change:
> > 014a7ec6c418 ("mk: add a paused deprecation warning before each build")
I can still see issues with UNH.
https://lab.dpdk.org/results/dashboard/patchsets/12024/
Can we get a fix quickly? I will have to reject reports from UNH otherwise.
--
David Marchand
prev parent reply other threads:[~2020-07-13 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 7:52 bugzilla
2020-07-13 8:34 ` David Marchand [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=CAJFAV8x35MRrua5JWThXzvgMAPWo1hU0Wz_zqPph+tjsHzuCUg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=ci@dpdk.org \
--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).