On 11/6/20 8:59 PM, Jakub Jelinek wrote:
I think I'll work with Martin early next week to think about further spots
to add logging, so we narrow down where it is still called and where it
isn't.

Hello.

I'm suggesting to use the following extra logging.

Martin
>From a39631f6515b60ae2a3c8de0129b9920471df18b Mon Sep 17 00:00:00 2001
From: marxin <mli...@suse.cz>
Date: Mon, 9 Nov 2020 08:56:44 +0100
Subject: [PATCH] Another debugging.

---
 sourceware/projects/src-home/git-hooks/hooks/post_receive.py | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/sourceware/projects/src-home/git-hooks/hooks/post_receive.py b/sourceware/projects/src-home/git-hooks/hooks/post_receive.py
index 0e931f8..37166e6 100644
--- a/sourceware/projects/src-home/git-hooks/hooks/post_receive.py
+++ b/sourceware/projects/src-home/git-hooks/hooks/post_receive.py
@@ -18,6 +18,7 @@ from updates.factory import new_update
 from utils import debug, warn
 
 import traceback
+import datetime
 
 def post_receive_one(ref_name, old_rev, new_rev, refs, submitter_email):
     """post-receive treatment for one reference.
@@ -35,6 +36,9 @@ def post_receive_one(ref_name, old_rev, new_rev, refs, submitter_email):
           '                        new_rev=%s)'
           % (ref_name, old_rev, new_rev))
 
+    with open("/tmp/gcc-git-mail.log", "a") as f:
+        ts = str(datetime.datetime.now())
+        f.write('post_receive_one:%s: ref_name=%s, old_rev=%s, new_rev=%s\n' % (ts, ref_name, old_rev, new_rev))
     update = new_update(ref_name, old_rev, new_rev, refs, submitter_email)
     if update is None:
         # We emit a warning, rather than trigger an assertion, because
-- 
2.29.2

Reply via email to