DPDK CI discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: sys_stv <sys_stv@intel.com>, "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: test-report@dpdk.org, longfengx.liang@intel.com,
	 Wei Ling <weix.ling@intel.com>,
	ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdk-test-report] (Testing) |FAILURE| pw(102710-102718) sid(19934) job(PER_PATCH_BUILD9081) [v6, 9/9] interrupts: extend event list
Date: Mon, 25 Oct 2021 09:00:03 +0200	[thread overview]
Message-ID: <CAJFAV8wz2t58F7OXxrdyHWbc_1VLQYc7duxYSYH2iDJiyXLV=g@mail.gmail.com> (raw)
In-Reply-To: <311d4e$it4ent@fmsmga001-auth.fm.intel.com>

On Mon, Oct 25, 2021 at 8:44 AM <sys_stv@intel.com> wrote:
>
>
> Test-Label: intel-Testing
> Test-Status: FAILURE
> http://dpdk.org/patch/102718
>
> _Testing issues_
>
> Submitter: David Marchand <david.marchand@redhat.com>
> Date: 2021-10-24 20:04:41
> Branch : dpdk
> CommitID: daa02b5cddbb8e11b31d41e2bf7bb1ae64dcae2f
>
> Testing Summary : 8 Case Done, 6 Successful, 2 Failures
>
> TestPlan:
>         pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test.rst
>         vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test.rst
>         virtio_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/virtio_smoke_test_plan.rst
>
> TestSuite:
>         pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
>         vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
>         virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py
>
>
> OS : Ubuntu 20.04.3 LTS
> Kernel : 5.8.0-48-generic
> GCC : 10.3.0-1ubuntu1~20.04
> NIC : Ethernet Controller E810-C for SFP
> Target : x86_64-native-linuxapp-gcc
>
>         Test result details:
>         +-------------+---------------------+-------+
>         | suite       | case                | status|
>         +-------------+---------------------+-------+
>         | pf_smoke    | test_pf_tx_rx_queue | passed|
>         | pf_smoke    | test_pf_jumbo_frames| passed|
>         | pf_smoke    | test_pf_rss         | FAILED|
>         | vf_smoke    | test_vf_tx_rx_queue | passed|
>         | vf_smoke    | test_vf_jumbo_frames| passed|
>         | vf_smoke    | test_vf_rss         | FAILED|
>         | virtio_smoke| test_virtio_pvp     | passed|
>         | virtio_smoke| test_virtio_loopback| passed|
>         +-------------+---------------------+-------+
>

This report is useless.

Some links to testplans are wrong (try clicking the first one).
There is no logs to know what is wrong.


Please confirm I can safely ignore it.



--
David Marchand


       reply	other threads:[~2021-10-25  7:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <311d4e$it4ent@fmsmga001-auth.fm.intel.com>
2021-10-25  7:00 ` David Marchand [this message]
2021-10-25 19:22   ` 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='CAJFAV8wz2t58F7OXxrdyHWbc_1VLQYc7duxYSYH2iDJiyXLV=g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=ci@dpdk.org \
    --cc=longfengx.liang@intel.com \
    --cc=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=weix.ling@intel.com \
    --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).