From: "Martin Storsjö" <martin@martin.st> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [FATE PATCH] Properly list test errors when there are no failed tests Date: Fri, 27 Jun 2025 15:43:58 +0300 (EEST) Message-ID: <ad1b4bbb-efd4-5e21-68ea-b84f3494bf2@martin.st> (raw) In-Reply-To: <20250618015000.GN29660@pb2> On Wed, 18 Jun 2025, Michael Niedermayer wrote: > Hi Martin > > On Fri, Jun 13, 2025 at 01:57:05PM +0300, Martin Storsjö wrote: >> If there were failures while running tests, e.g. if failing to >> compile checkasm or any other of the test programs, there are no >> failed tests per se, and the number of succeessful tests is >> equal to the total number of tests. >> >> For these cases, check the job status code instead of declaring >> them as a full success. >> --- >> history.cgi | 2 +- >> index.cgi | 2 +- >> report.cgi | 6 +++++- >> 3 files changed, 7 insertions(+), 3 deletions(-) > > sounds reasonable, but ill leave the perl review to someone who actually > knows perl I've tested it locally, so if we have nobody else volunteering to review it, is that enough? > Its a few years since the last change to fateserver, i think we dont > have a script to update the checkout on the server from a git push. > Its a while, i dont remember exactly :) > so you have to update that checkout after pushing possibly I don't think I have access to any such server, but if it's ok with you can I (try to) push this patch to the gitosis repo, and then ask some admin (Timo?) to possibly update a checkout somewhere. // 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".
next prev parent reply other threads:[~2025-06-27 12:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-13 10:57 Martin Storsjö 2025-06-18 1:50 ` Michael Niedermayer 2025-06-27 12:43 ` Martin Storsjö [this message] 2025-06-27 19:03 ` Kacper Michajlow 2025-06-27 19:06 ` Martin Storsjö 2025-06-28 1:53 ` Michael Niedermayer
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=ad1b4bbb-efd4-5e21-68ea-b84f3494bf2@martin.st \ --to=martin@martin.st \ --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