From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 471] failing to build test from app/test
Date: Wed, 13 May 2020 08:33:05 +0000 [thread overview]
Message-ID: <bug-471-3-zyfA2Rk07m@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-471-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=471
Vipin Varghese (vipin.varghese@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Status|RESOLVED |UNCONFIRMED
--- Comment #2 from Vipin Varghese (vipin.varghese@intel.com) ---
If I run from the target folder `make test`
```
# make test
/home/saesrv02/Downloads/dpdksrc/dpdk/x86_64-native-linuxapp-gcc/app/test -c f
Running tests with 4 workers
Test name Test result Test Total
================================================================================
Skipped autotests:
dump_physmem: Skipped [Not compiled] [00m 00s]
dump_memzone: Skipped [Not compiled] [00m 00s]
dump_struct_sizes: Skipped [Not compiled] [00m 00s]
dump_mempool: Skipped [Not compiled] [00m 00s]
dump_malloc_stats: Skipped [Not compiled] [00m 00s]
dump_devargs: Skipped [Not compiled] [00m 00s]
dump_log_types: Skipped [Not compiled] [00m 00s]
dump_ring: Skipped [Not compiled] [00m 00s]
Cycles autotest: Fail [00m 01s][00m 02s]
EAL flags autotest: Fail [00m 02s][00m 05s]
Read/write lock autotest: Fail [Timeout] [00m 10s][00m 13s]
Alarm autotest: Fail [00m 00s][00m 37s]
PMD ring autotest: Fail [00m 00s][00m 55s]
Link bonding autotest: Fail [00m 00s][01m 11s]
Link bonding mode4 autotest: Fail [00m 00s][01m 12s]
Link bonding rssconf autotest:Fail [00m 00s][01m 12s]
```
1. should not for Link-Bond test either use `vdev` or `Skip` rather than
failing if the desired number of ports is not available?
2. why would `EAL, Alarm, Lock` fail as it is the library and not PMD?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-05-13 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 8:24 bugzilla
2020-05-13 8:27 ` bugzilla
2020-05-13 8:33 ` bugzilla [this message]
2020-05-13 8:41 ` bugzilla
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=bug-471-3-zyfA2Rk07m@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).