Stefano Brivio <sbrivio@xxxxxxxxxx> wrote: > On Fri, 7 Feb 2020 11:34:42 +0100 > Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx> wrote: > > > On Thu, Jan 30, 2020 at 01:16:58AM +0100, Stefano Brivio wrote: > > > This test checks that set elements can be added, deleted, that > > > addition and deletion are refused when appropriate, that entries > > > time out properly, and that they can be fetched by matching values > > > in the given ranges. > > > > I'll keep this back so Phil doesn't have to do some knitting work > > meanwhile the tests finishes for those 3 minutes. > > But I wanted to see his production :( > > > If this can be shortened, better. Probably you can add a parameter to > > enable the extra torture test mode not that is away from the > > ./run-test.sh path. > > I can't think of an easy way to remove that sleep(1), I could decrease > the timeouts passed to nft but then there's no portable way to wait for > less than one second. Even busybox' sleep can do 'sleep 0.01', do we really need to be *that* portable?