From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] fate.sh: Allow overriding what targets to make for running the tests
Date: Fri, 01 Dec 2023 14:06:54 +0200
Message-ID: <FD20219B-C4DC-41E8-9190-86E1CC38DD8F@remlab.net> (raw)
In-Reply-To: <9b9ee64-fcc6-181e-5043-19cd98be6184@martin.st>
Le 1 décembre 2023 09:55:15 GMT+02:00, "Martin Storsjö" <martin@martin.st> a écrit :
>On Fri, 1 Dec 2023, Rémi Denis-Courmont wrote:
>
>> Le 30 novembre 2023 23:13:59 GMT+02:00, "Martin Storsjö" <martin@martin.st> a écrit :
>>> On Thu, 30 Nov 2023, Rémi Denis-Courmont wrote:
>>
>>>> In other words, is publishing on the FATE website worth making the tests coverage and/or the build time worse?
>>>
>>> By making the test coverage worse, you mean if I'd be doing the full testing of many combinations already, and I'd stop doing that in order to do this lesser testing instead? If I'd be doing it (I currently don't) I guess that would be my concern, not others?
>>
>> No. The point is that this is adding a small hack that works for one specific case for a short while (testing Armv8 IMM8 and DP), but is known not to be sufficient anyway (for SVE, PAuth, RVV, etc).
>
>I'll reiterate the question from the bottom of the mail, that you didn't respond to.
>
>Would you be ok with a setup, where a FATE instance optionally can run a subset of tests instead of the full suite, but run them multiple times with e.g. different QEMU settings? That would allow repeating checkasm for all the interesting cases - and if one really wanted to spend a lot of CPU time on it, also could run the full FATE suite in all those configurations.
Being able to run tests under a different runner/wrapper or the same runner with different settings, would be a lot more viable, indeed IMO
>
>// Martin
>_______________________________________________
>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".
_______________________________________________
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-12-01 12:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 12:31 Martin Storsjö
2023-11-27 15:46 ` Rémi Denis-Courmont
2023-11-27 21:55 ` Martin Storsjö
2023-11-30 11:05 ` Martin Storsjö
2023-11-30 14:23 ` Rémi Denis-Courmont
2023-11-30 15:34 ` Martin Storsjö
2023-11-30 16:03 ` Rémi Denis-Courmont
2023-11-30 16:28 ` Martin Storsjö
2023-11-30 17:37 ` Rémi Denis-Courmont
2023-11-30 21:13 ` Martin Storsjö
2023-12-01 7:36 ` Rémi Denis-Courmont
2023-12-01 7:55 ` Martin Storsjö
2023-12-01 12:06 ` Rémi Denis-Courmont [this message]
2023-11-27 22:10 ` Alexander Strasser
2023-11-27 23:22 ` Michael Niedermayer
2023-11-28 7:27 ` Rémi Denis-Courmont
2023-11-28 14:21 ` Michael Niedermayer
2023-11-30 15:52 ` Rémi Denis-Courmont
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=FD20219B-C4DC-41E8-9190-86E1CC38DD8F@remlab.net \
--to=remi@remlab.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