From: "Martin Storsjö" <martin@martin.st> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [FATE PATCH] Properly list test errors when there are no failed tests Date: Fri, 13 Jun 2025 13:57:05 +0300 Message-ID: <20250613105709.2065708-1-martin@martin.st> (raw) 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(-) diff --git a/history.cgi b/history.cgi index 533999c..d0a855d 100755 --- a/history.cgi +++ b/history.cgi @@ -76,7 +76,7 @@ for my $date ((sort { $b cmp $a } @reps)[0..49]) { td $$rep{nwarn}; if ($npass) { $rtext = "$npass / $ntest"; - $rclass = $npass==$ntest? 'pass' : $npass? 'warn' : 'fail'; + $rclass = $$rep{status}==0? 'pass' : $npass? 'warn' : 'fail'; } elsif (!$ntest and !$$rep{status}) { $rtext = "build only"; $rclass = $$rep{status}? 'fail' : 'pass'; diff --git a/index.cgi b/index.cgi index 25c61e9..89e599a 100755 --- a/index.cgi +++ b/index.cgi @@ -286,7 +286,7 @@ for my $rep (sort repcmp @reps) { td $$rep{comment}, class => 'comment'; if ($npass) { $rtext = "$npass / $ntest"; - $rclass = $npass==$ntest? 'pass' : $npass? 'warn' : 'fail'; + $rclass = $$rep{status}==0? 'pass' : $npass? 'warn' : 'fail'; } elsif (!$ntest and !$$rep{status}) { $rtext = "build only"; $rclass = $$rep{status}? 'fail' : 'pass'; diff --git a/report.cgi b/report.cgi index 5a2394d..ca003b1 100755 --- a/report.cgi +++ b/report.cgi @@ -183,7 +183,11 @@ if ($nfail) { } end 'tbody'; } elsif ($ntest) { - start 'tr', class => 'pass'; th 'All tests successful', colspan => 3; end; + if ($$hdr{status}) { + start 'tr', class => 'fail'; th 'Failure building tests', colspan => 3; end; + } else { + start 'tr', class => 'pass'; th 'All tests successful', colspan => 3; end; + } } else { my $class = $$hdr{status}? 'fail' : 'pass'; start 'tr', class => $class; th 'No tests were run', colspan => 3; end; -- 2.43.0 _______________________________________________ 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 reply other threads:[~2025-06-13 10:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-13 10:57 Martin Storsjö [this message] 2025-06-18 1:50 ` 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=20250613105709.2065708-1-martin@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