From: David Marchand <david.marchand@redhat.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>, "ci@dpdk.org" <ci@dpdk.org>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [PATCH v2] build: increase minimum meson version to 0.53.2
Date: Mon, 10 Oct 2022 09:48:09 +0200 [thread overview]
Message-ID: <CAJFAV8xQJnDRdQLKhyO=y65Ta1NO7cmhdGrc0-hwm6u22ksVNw@mail.gmail.com> (raw)
In-Reply-To: <CY5PR11MB6187775765969A4ABE5FF42DF5209@CY5PR11MB6187.namprd11.prod.outlook.com>
On Mon, Oct 10, 2022 at 7:23 AM Tu, Lijuan <lijuan.tu@intel.com> wrote:
> > It seems the "intel-Testing" test is in ... berserk mode and spewing errors for all
> > patches since 10/03.
> > No clue if we have an issue in the main branch, and this test logs are useless.
> >
> > I'll wait for Intel PRC to be back and ignore for now.
>
> Yes, the main branch had an issue and has been fixed now. Intel-Testing is back to normal. It works fine.
The only info we had was that "something" was broken.
Example: http://mails.dpdk.org/archives/test-report/2022-October/313054.html
When other CI report a failure, executed commands and logs are
available in GHA and UNH dashboard, downloadable as zip files.
So it is relatively easy to figure out if the issue was due to an
infrastructure problem or if it was a test failure.
I don't think Intel CI provide such info. If this is the case, please
document it.
Otherwise, please Intel CI team, work on providing the same kind of info.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2022-10-10 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220912170747.3128065-1-bruce.richardson@intel.com>
[not found] ` <20221007162404.1117056-1-bruce.richardson@intel.com>
2022-10-07 19:13 ` David Marchand
2022-10-10 5:23 ` Tu, Lijuan
2022-10-10 7:48 ` David Marchand [this message]
2022-10-13 12:51 ` Tu, Lijuan
2022-10-10 14:53 ` David Marchand
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='CAJFAV8xQJnDRdQLKhyO=y65Ta1NO7cmhdGrc0-hwm6u22ksVNw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=lijuan.tu@intel.com \
--cc=lylavoie@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=zhaoyan.chen@intel.com \
/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).