From: David Marchand <david.marchand@redhat.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>,
"Gao, DaxueX" <daxuex.gao@intel.com>,
"Huang, ChenyuX" <chenyux.huang@intel.com>
Cc: ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: Diagnosing CI Failures Question
Date: Thu, 16 Mar 2023 17:59:44 +0100 [thread overview]
Message-ID: <CAJFAV8wm2imS7wF7nQ6FYpMchXsu2g30=iAZN4Hh3b3LtLhpYg@mail.gmail.com> (raw)
In-Reply-To: <20230316165126.GB8277@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
Hi Tyler,
On Thu, Mar 16, 2023 at 5:51 PM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
>
> I am a little lost how I investigate failures that come from the
> ci/intel-Functional tests. I'm still learning and about how to best
> utilize these resources.
>
> Is there a way I can get access to the artifacts from the failure? I
> notice this set of tests is most often the one that fails.
>
> Are the tests run here publicly available somehow? If so I would lobby
> to onboard them to my internal lab to save time by running it prior to
> submission.
>
> I'm also a bit concerned that this exact same failure is produced for
> two entirely separate patch series, but without more detail it's hard to
> tell if that is just a coincidence.
Tyler, I am lost too... those failures started to appear overnight.
This comes from the Intel CI.
I have neither log or nor aware of how to reproduce this.
Let's ask Intel people who were Cc'd on the report...
Daxue, Huang, please, can you enlighten us on what is wrong with this series?
For the context, see:
http://mails.dpdk.org/archives/test-report/2023-March/371507.html
Thanks.
--
David Marchand
next parent reply other threads:[~2023-03-16 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316165126.GB8277@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
2023-03-16 16:59 ` David Marchand [this message]
2023-03-17 4:27 ` Huang, ChenyuX
2023-03-17 14:59 ` Tyler Retzlaff
2023-03-21 10:10 ` David Marchand
2023-03-22 1:02 ` Gao, DaxueX
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='CAJFAV8wm2imS7wF7nQ6FYpMchXsu2g30=iAZN4Hh3b3LtLhpYg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=chenyux.huang@intel.com \
--cc=ci@dpdk.org \
--cc=daxuex.gao@intel.com \
--cc=roretzla@linux.microsoft.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).