This is an automated email from the git hooks/post-receive script.

Git pushed a commit to branch master
in repository ffmpeg.

The following commit(s) were added to refs/heads/master by this push:
     new acf6b520c1 fftools/ffmpeg_sched: do not print error code
acf6b520c1 is described below

commit acf6b520c1e73707190c0a591735ee8c7fbe8f58
Author:     Nicolas George <[email protected]>
AuthorDate: Sun Aug 3 20:25:03 2025 +0200
Commit:     Nicolas George <[email protected]>
CommitDate: Mon Jul 27 13:38:20 2026 +0200

    fftools/ffmpeg_sched: do not print error code
    
    The error codes are meaningless to users, especially
    the ones that do not come from standard errno codes.
---
 fftools/ffmpeg_sched.c | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/fftools/ffmpeg_sched.c b/fftools/ffmpeg_sched.c
index 8ec3bdaf80..88b3bf3177 100644
--- a/fftools/ffmpeg_sched.c
+++ b/fftools/ffmpeg_sched.c
@@ -2776,7 +2776,7 @@ static void *task_wrapper(void *arg)
     ret = task->func(task->func_arg);
     if (ret < 0)
         av_log(task->func_arg, AV_LOG_ERROR,
-               "Task finished with error code: %d (%s)\n", ret, 
av_err2str(ret));
+               "Task finished with error: %s\n", av_err2str(ret));
 
     err = task_cleanup(sch, task->node);
     ret = err_merge(ret, err);
@@ -2791,9 +2791,12 @@ static void *task_wrapper(void *arg)
         pthread_mutex_unlock(&sch->finish_lock);
     }
 
-    av_log(task->func_arg, ret < 0 ? AV_LOG_ERROR : AV_LOG_VERBOSE,
-           "Terminating thread with return code %d (%s)\n", ret,
-           ret < 0 ? av_err2str(ret) : "success");
+    if (ret < 0)
+        av_log(task->func_arg, AV_LOG_ERROR,
+               "Terminating thread with error: %s\n", av_err2str(ret));
+    else
+        av_log(task->func_arg, AV_LOG_VERBOSE,
+               "Terminating thread with success\n");
 
     return (void*)(intptr_t)ret;
 }

_______________________________________________
ffmpeg-cvslog mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to