From: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>
To: "dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
Test Report <test-report@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [dpdk-test-report] |FAILURE| pw97549 [PATCH] [v2] eventdev: rx-adapter: improve enqueue buffer to circular buffer
Date: Tue, 31 Aug 2021 12:23:00 +0000 [thread overview]
Message-ID: <CO1PR11MB4882B22CAC5932520C965EFD87CC9@CO1PR11MB4882.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210831034330.9D6A889060@noxus.dpdklab.iol.unh.edu>
Hi,
Any idea on why atomic_autotest is failing for this patch with only changes to commit header?
In this malloc_autotest got passed without any changes in sources whereas it got failed for first patch - https://lab.dpdk.org/results/dashboard/patchsets/18384/
Thanks,
Ganapati
> -----Original Message-----
> From: dpdklab@iol.unh.edu <dpdklab@iol.unh.edu>
> Sent: 31 August 2021 09:14
> To: Test Report <test-report@dpdk.org>
> Cc: dpdklab@iol.unh.edu; Kundapura, Ganapati
> <ganapati.kundapura@intel.com>
> Subject: |FAILURE| pw97549 [PATCH] [v2] eventdev: rx-adapter: improve
> enqueue buffer to circular buffer
>
> Test-Label: iol-aarch64-unit-testing
> Test-Status: FAILURE
> http://dpdk.org/patch/97549
>
> _Testing issues_
>
> Submitter: Ganapati Kundapura <ganapati.kundapura@intel.com>
> Date: Monday, August 30 2021 13:06:25
> DPDK git baseline: Repo:dpdk
> Branch: master
> CommitID:bfd3c352eb9729f97da6e1b5e958e121542d8a8d
>
> 97549 --> 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 1.16s
> 86/94 DPDK:fast-tests / trace_autotest OK 1.95s
> 87/94 DPDK:fast-tests / telemetry_json_autotest OK 2.25s
> 88/94 DPDK:fast-tests / telemetry_data_autotest OK 0.99s
> 89/94 DPDK:fast-tests / ring_pmd_autotest OK 1.13s
> 90/94 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 3.51s
> 91/94 DPDK:fast-tests / bitratestats_autotest OK 1.14s
> 92/94 DPDK:fast-tests / latencystats_autotest OK 1.13s
> 93/94 DPDK:fast-tests / pdump_autotest OK 5.96s
> 94/94 DPDK:fast-tests / compressdev_autotest SKIP 2.31s 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/18412/
>
> UNH-IOL DPDK Community Lab
>
> To manage your email subscriptions, visit:
> https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2021-09-03 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 3:43 dpdklab
2021-08-31 12:23 ` Kundapura, Ganapati [this message]
2021-08-31 14:47 ` [dpdk-test-report] [dpdklab] " Brandon Lo
2021-09-01 14:45 ` Kundapura, Ganapati
-- strict thread matches above, loose matches on Subject: below --
2021-08-31 2:33 [dpdk-test-report] " dpdklab
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=CO1PR11MB4882B22CAC5932520C965EFD87CC9@CO1PR11MB4882.namprd11.prod.outlook.com \
--to=ganapati.kundapura@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dpdklab@iol.unh.edu \
--cc=jerinjacobk@gmail.com \
--cc=test-report@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).