From: Aaron Conole <aconole@redhat.com> To: Thomas Monjalon <thomas@monjalon.net> Cc: msantana@redhat.com, David Marchand <david.marchand@redhat.com>, dev@dpdk.org, ci@dpdk.org Subject: Re: [dpdk-dev] [PATCH 00/14] Unit tests fixes for CI Date: Mon, 01 Jul 2019 08:17:45 -0400 Message-ID: <f7tsgrq0x06.fsf@dhcp-25.97.bos.redhat.com> (raw) In-Reply-To: <2134880.WhL1dmy7PZ@xps> (Thomas Monjalon's message of "Thu, 27 Jun 2019 18:34:18 +0200") Thomas Monjalon <thomas@monjalon.net> writes: > 04/06/2019 17:49, Michael Santana Francisco: >> On 6/4/19 4:59 AM, David Marchand wrote: >> > - the "perf" tests are taking way too long for my taste, +1 here. >> >> We should still fix them. However I don't know if we should be running >> the perf test for every job and every patch on travis. It takes too >> long. The travis queue will be delayed too far behind for it to be of >> any use. >> >> OTOH we could have one job as part of the travis build dedicated to >> running tests (or just perf test). It's still time consuming but better >> than running the test on every travis job. For this to work we would >> need to decreased the timeout for the perf tests as the timeout for it >> and the travis are both 10 minutes > > +Cc ci@dpdk.org > > I don't think we should run the perf tests in basic CI like Travis. > We can run perf tests if the purpose is to compare the performance > with previous releases, as some other tests in the community lab. +1 - some of the perf tests aren't going to complete in any sort of reasonable time. While we could claim it's a separate problem, we should also not enable something that will make the travis runs so much longer. I do like the idea of running tests in the travis build, and I think it would make sense to have just a single job for it (or maybe one for clang and one for gcc? maybe even that is overkill). I would rather not do performance tests during the travis run, though. It doesn't really make sense. Travis isn't any kind of an 'optimized' environment, so I don't know what 'performance' should mean.
next prev parent reply index Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-04 8:59 David Marchand 2019-06-04 8:59 ` [dpdk-dev] [PATCH 01/14] test/bonding: add missing sources for link bonding RSS David Marchand 2019-06-04 12:59 ` Aaron Conole 2019-06-04 8:59 ` [dpdk-dev] [PATCH 02/14] test/crypto: move tests to the driver specific list David Marchand 2019-06-04 13:00 ` Aaron Conole 2019-06-04 8:59 ` [dpdk-dev] [PATCH 03/14] test/eventdev: " David Marchand 2019-06-04 13:04 ` Aaron Conole 2019-06-04 8:59 ` [dpdk-dev] [PATCH 04/14] test/hash: fix off-by-one check on core count David Marchand 2019-06-04 13:05 ` Aaron Conole 2019-06-05 20:02 ` Wang, Yipeng1 2019-06-04 8:59 ` [dpdk-dev] [PATCH 05/14] test/hash: rectify slaveid to point to valid cores David Marchand 2019-06-05 20:02 ` Wang, Yipeng1 2019-06-04 8:59 ` [dpdk-dev] [PATCH 06/14] test/hash: clean remaining trace of scaling autotest David Marchand 2019-06-04 13:31 ` Aaron Conole 2019-06-04 8:59 ` [dpdk-dev] [PATCH 07/14] test/latencystats: fix stack smashing David Marchand 2019-06-04 13:38 ` Aaron Conole 2019-06-04 8:59 ` [dpdk-dev] [PATCH 08/14] test/stack: fix lock-free test name David Marchand 2019-06-04 13:06 ` Aaron Conole 2019-06-04 8:59 ` [dpdk-dev] [PATCH 09/14] test/eal: set memory channel config only in dedicated test David Marchand 2019-06-04 13:11 ` Aaron Conole 2019-06-26 9:44 ` Burakov, Anatoly 2019-06-04 8:59 ` [dpdk-dev] [PATCH 10/14] test/eal: set core mask/list " David Marchand 2019-06-04 13:12 ` Aaron Conole 2019-06-26 9:45 ` Burakov, Anatoly 2019-06-04 8:59 ` [dpdk-dev] [PATCH 11/14] test/eal: check number of cores before running subtests David Marchand 2019-06-04 13:26 ` Aaron Conole 2019-06-26 9:47 ` Burakov, Anatoly 2019-06-04 8:59 ` [dpdk-dev] [PATCH 12/14] test/eal: make the test pass again David Marchand 2019-06-04 13:29 ` Aaron Conole 2019-06-04 13:50 ` David Marchand 2019-06-26 9:49 ` Burakov, Anatoly 2019-06-26 10:03 ` David Marchand 2019-06-04 8:59 ` [dpdk-dev] [PATCH 13/14] test: do not start tests in parallel David Marchand 2019-06-04 8:59 ` [dpdk-dev] [PATCH 14/14] test: skip tests when missing requirements David Marchand 2019-06-07 20:54 ` Honnappa Nagarahalli 2019-06-08 8:01 ` David Marchand 2019-06-11 4:08 ` Honnappa Nagarahalli 2019-06-04 15:49 ` [dpdk-dev] [PATCH 00/14] Unit tests fixes for CI Michael Santana Francisco 2019-06-27 16:34 ` Thomas Monjalon 2019-07-01 12:17 ` Aaron Conole [this message] 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 00/15] " David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 01/15] test/bonding: add missing sources for link bonding RSS David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 02/15] test/crypto: move tests to the driver specific list David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 03/15] test/eventdev: " David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 04/15] test/hash: fix off-by-one check on core count David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 05/15] test/hash: rectify slaveid to point to valid cores David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 06/15] test/hash: clean remaining trace of scaling autotest David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 07/15] test/latencystats: fix stack smashing David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 08/15] test/rcu: remove arbitrary limit on max core count David Marchand 2019-06-28 12:56 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit 2019-06-28 13:32 ` David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 09/15] test/stack: fix lock-free test name David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 10/15] test/eal: set memory channel config only in dedicated test David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 11/15] test/eal: set core mask/list " David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 12/15] test/eal: check number of cores before running subtests David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 13/15] test: split into shorter subtests for CI David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 14/15] test: do not start tests in parallel David Marchand 2019-06-15 6:42 ` [dpdk-dev] [PATCH v2 15/15] test: skip tests when missing requirements David Marchand 2019-06-17 10:00 ` [dpdk-dev] [PATCH v2 00/15] Unit tests fixes for CI Bruce Richardson 2019-06-17 10:46 ` David Marchand 2019-06-17 11:17 ` Bruce Richardson 2019-06-17 11:41 ` David Marchand 2019-06-17 11:56 ` Bruce Richardson 2019-06-17 13:44 ` David Marchand 2019-06-27 20:36 ` Thomas Monjalon 2019-07-01 16:04 ` Aaron Conole 2019-07-01 16:22 ` Thomas Monjalon 2019-07-01 16:45 ` David Marchand 2019-07-01 18:07 ` Michael Santana Francisco 2019-07-09 15:50 ` Michael Santana Francisco 2019-07-10 8:18 ` David Marchand
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=f7tsgrq0x06.fsf@dhcp-25.97.bos.redhat.com \ --to=aconole@redhat.com \ --cc=ci@dpdk.org \ --cc=david.marchand@redhat.com \ --cc=dev@dpdk.org \ --cc=msantana@redhat.com \ --cc=thomas@monjalon.net \ /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
DPDK-dev Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \ dev@dpdk.org public-inbox-index dpdk-dev Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git