From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] fate.sh: Allow overriding what targets to make for running the tests
Date: Mon, 27 Nov 2023 17:46:40 +0200
Message-ID: <12696030.Brfu6Qr6Id@basile.remlab.net> (raw)
In-Reply-To: <20231127123118.3622784-1-martin@martin.st>
Le maanantaina 27. marraskuuta 2023, 14.31.18 EET Martin Storsjö a écrit :
> This can be useful if doing testing of uncommon CPU extensions by
> running tests with QEMU (by configuring with e.g.
> "target_exec=qemu-aarch64"), by only running the checkasm tests,
> to get a reasonable test coverage without excessive test runtime.
For the purpose of testing future or bleeding-edge CPU extensions on emulator,
you would normally want to be able to actually filter those in. That is more of
a matter of patching checkasm than FATE.
Considering the poor coverage of checkasm, I fear that this just gives the
wrong impression, not to say a false sense of security. It feels misleading to
encourage or support that paradigm into FATE, in light of that poor coverage.
Afterall, if it's just about running checkasm, anybody can just run
`make tests/checkasm/checkasm && tests/checkasm/checkasm`.
Either way, this feels like a case of cart before horse.
Also FWIW, RV broke due to misaligned accesses and illegal vector types that
QEMU tolerated. That is rather an argument against QEMU than against this MR
but still.
--
Rémi Denis-Courmont
http://www.remlab.net/
_______________________________________________
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-11-27 15:47 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 [this message]
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
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=12696030.Brfu6Qr6Id@basile.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