> -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, June 08, 2016 12:40 PM > To: Jastrzebski, MichalX K <michalx.k.jastrzebski at intel.com>; Iremonger, > Bernard <bernard.iremonger at intel.com> > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH] app/test: fix bond device name too long > > 2016-05-27 18:38, Thomas Monjalon: > > 2016-05-27 17:20, Michal Jastrzebski: > > > Bond device name was too long (grather than 32 signs) that > > > cause mempool allocation to fail. > > > > Maybe that this kind of failure would be avoided if the test > > was added to autotests (app/test/autotest_data.py). > > > > Generally speaking, it would be a good idea to make an audit > > on which tests are missing in "make fast_test" and "make test". > > Any comment please?
Hi Thomas, There is a small timeout in test_tlb_tx_burst - big burst has to be generated to detect balancing and small timeout has to be included between each burst, thus I am not sure if link_bonding_autotest can be classified to fast tests (test takes about 3-4 seconds). We can add this test to autotests script for which time is not so critical. Best regards Michal