[dpdk-dev] [Bug 471] failing to build test from app/test
bugzilla at dpdk.org
bugzilla at dpdk.org
Wed May 13 10:33:05 CEST 2020
https://bugs.dpdk.org/show_bug.cgi?id=471
Vipin Varghese (vipin.varghese at intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Status|RESOLVED |UNCONFIRMED
--- Comment #2 from Vipin Varghese (vipin.varghese at 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.
More information about the dev
mailing list