From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] lib/tests: Remove tst_fuzzy_sync02
Date: Tue, 31 Aug 2021 13:35:09 +0100 [thread overview]
Message-ID: <875yvllrlu.fsf@suse.de> (raw)
In-Reply-To: <20210831121250.17557-1-pvorel@suse.cz>
Hello Petr,
Petr Vorel <pvorel@suse.cz> writes:
> tst_fuzzy_sync02 is not stable enough [1]:
>
> ../../include/tst_fuzzy_sync.h:346: TINFO: loop = 10001, delay_bias = 3960
> ../../include/tst_fuzzy_sync.h:335: TINFO: start_a - start_b: { avg = -8859ns, avg_dev = 66ns, dev_ratio = 0.01 }
> ../../include/tst_fuzzy_sync.h:335: TINFO: end_a - start_a : { avg = 17160ns, avg_dev = 85ns, dev_ratio = 0.00 }
> ../../include/tst_fuzzy_sync.h:335: TINFO: end_b - start_b : { avg = 18474ns, avg_dev = 55ns, dev_ratio = 0.00 }
> ../../include/tst_fuzzy_sync.h:335: TINFO: end_a - end_b : { avg = -10173ns, avg_dev = 124ns, dev_ratio = 0.01 }
> ../../include/tst_fuzzy_sync.h:335: TINFO: spins : { avg = 2751 , avg_dev = 31 , dev_ratio = 0.01 }
> ../../include/tst_fuzzy_sync.h:685: TINFO: Exceeded execution loops, requesting exit
> tst_fuzzy_sync02.c:169: TFAIL: 2| =:48
> ...
> runtest TINFO: === C TEST RESULTS ===
> ...
> runtest TINFO: 1x TFAIL: tst_fuzzy_sync02
>
> Both tst_fuzzy_sync0{1,2} occasionally fails (restart helps). But
> tst_fuzzy_sync03 is stable thus we have at least smoke test for fuzzy
> sync.
Yes, there is probably some work to do on the algorithm itself. At least
to make it stable in this kind of environment.
Reviewed-by: Richard Palethorpe <rpalethorpe@suse.com>
--
Thank you,
Richard.
next prev parent reply other threads:[~2021-08-31 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 12:12 [LTP] [PATCH 1/1] lib/tests: Remove tst_fuzzy_sync02 Petr Vorel
2021-08-31 12:29 ` Cyril Hrubis
2021-08-31 12:35 ` Richard Palethorpe [this message]
2021-08-31 12:43 ` Li Wang
2021-08-31 12:54 ` Petr Vorel
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=875yvllrlu.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
/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