From: Anton Khirnov <anton@khirnov.net> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH 2/2] tests/fate-run: add testing with a random number of threads Date: Fri, 23 Jun 2023 16:41:47 +0200 Message-ID: <20230623144147.7940-2-anton@khirnov.net> (raw) In-Reply-To: <20230623144147.7940-1-anton@khirnov.net> Useful for discovering bugs that depend on a specific thread count. Uses a simple PRNG copied from random() from libavutil/eval.c Use like THREADS=randomX for a random thread count from 1 to X, with X=16 when not specified. --- doc/fate.texi | 5 +++++ tests/fate-run.sh | 9 +++++++++ 2 files changed, 14 insertions(+) diff --git a/doc/fate.texi b/doc/fate.texi index 8450856015..13aea7a21f 100644 --- a/doc/fate.texi +++ b/doc/fate.texi @@ -223,6 +223,11 @@ meaning only while running the regression tests. Specify how many threads to use while running regression tests, it is quite useful to detect thread-related regressions. +This variable may be set to the string "random", optionally followed by a +number, like "random99", This will cause each test to use a random number of +threads. If a number is specified, it is used as a maximum number of threads, +otherwise 16 is the maximum. + @item THREAD_TYPE Specify which threading strategy test, either @samp{slice} or @samp{frame}, by default @samp{slice+frame} diff --git a/tests/fate-run.sh b/tests/fate-run.sh index e12279e4cf..55c579f84e 100755 --- a/tests/fate-run.sh +++ b/tests/fate-run.sh @@ -33,6 +33,15 @@ errfile="${outdir}/${test}.err" cmpfile="${outdir}/${test}.diff" repfile="${outdir}/${test}.rep" +case $threads in + random*) + threads_max=${threads#random} + [ -z "$threads_max" ] && threads_max=16 + threads="mod(time(0)*1664525+1013904223,$threads_max)+1" + ;; +esac + + target_path(){ test ${1} = ${1#/} && p=${target_path}/ echo ${p}${1} -- 2.40.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-06-23 14:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-23 14:41 [FFmpeg-devel] [PATCH 1/2] lavu/tests/cpu: stop processing the thread count Anton Khirnov 2023-06-23 14:41 ` Anton Khirnov [this message] 2023-07-07 10:42 ` [FFmpeg-devel] [PATCH] tests/fate-run: add testing with a random number of threads Anton Khirnov
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=20230623144147.7940-2-anton@khirnov.net \ --to=anton@khirnov.net \ --cc=ffmpeg-devel@ffmpeg.org \ /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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/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 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git