From: "Szwed, Maciej" <maciej.szwed@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] |FAILURE| pw97277 [PATCH] [v4] eal: read data buffer on RTE_INTR_HANDLE_VFIO_REQ
Date: Mon, 30 Aug 2021 09:34:02 +0000 [thread overview]
Message-ID: <BL0PR11MB294853DA66E669C0473AC86497CB9@BL0PR11MB2948.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210825205901.594F789060@noxus.dpdklab.iol.unh.edu>
Hi,
I'm new to posting patches to DPDK repository. I've submitted a patch recently and one of the tests performed on it failed. I went through the failed test log and it looks like it does not have anything to do with my patch. You can check details below. What should be the next steps I should perform?
Thanks,
Maciek
-----Original Message-----
From: dpdklab@iol.unh.edu <dpdklab@iol.unh.edu>
Sent: Wednesday, August 25, 2021 10:59 PM
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu; Szwed, Maciej <maciej.szwed@intel.com>
Subject: |FAILURE| pw97277 [PATCH] [v4] eal: read data buffer on RTE_INTR_HANDLE_VFIO_REQ
Test-Label: iol-aarch64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/97277
_Testing issues_
Submitter: Maciej Szwed <maciej.szwed@intel.com>
Date: Tuesday, August 24 2021 09:55:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fdab8f2e17493192d555cd88cf28b06269174326
97277 --> testing fail
Test environment and result as below:
+----------------------+----------------+--------------+
| Environment | dpdk_unit_test | lpm_autotest |
+======================+================+==============+
| Ubuntu 20.04 ARM | FAIL | SKIPPED |
+----------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS |
+----------------------+----------------+--------------+
==== 20 line log output for Ubuntu 20.04 ARM (dpdk_unit_test): ====
85/94 DPDK:fast-tests / thash_autotest OK 0.33s
86/94 DPDK:fast-tests / trace_autotest OK 0.39s
87/94 DPDK:fast-tests / telemetry_json_autotest OK 0.44s
88/94 DPDK:fast-tests / telemetry_data_autotest OK 0.41s
89/94 DPDK:fast-tests / ring_pmd_autotest OK 0.32s
90/94 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.53s
91/94 DPDK:fast-tests / bitratestats_autotest OK 0.29s
92/94 DPDK:fast-tests / latencystats_autotest OK 0.30s
93/94 DPDK:fast-tests / pdump_autotest OK 5.40s
94/94 DPDK:fast-tests / compressdev_autotest SKIP 0.41s exit status 77
Ok: 89
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 4
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Arm-gigabyte-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====
Ubuntu 20.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18334/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next parent reply other threads:[~2021-08-30 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210825205901.594F789060@noxus.dpdklab.iol.unh.edu>
2021-08-30 9:34 ` Szwed, Maciej [this message]
2021-09-03 8:59 ` Szwed, Maciej
2021-09-03 12:00 ` David Marchand
2021-09-21 11:23 ` Szwed, Maciej
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=BL0PR11MB294853DA66E669C0473AC86497CB9@BL0PR11MB2948.namprd11.prod.outlook.com \
--to=maciej.szwed@intel.com \
--cc=dev@dpdk.org \
/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).