Re: mail-sending error from git server updating "concurrency" branch

[Eli Zaretskii]

> From: Ken Raeburn <address@hidden>
> Date: Sun, 1 Nov 2015 01:19:52 -0500
> 
> I got this error back from the git server while pushing an update to the 
> “concurrency” branch:
> 
> > Counting objects: 222, done.
> > Delta compression using up to 2 threads.
> > Compressing objects: 100% (153/153), done.
> > Writing objects: 100% (222/222), 42.20 KiB | 0 bytes/s, done.
> > Total 222 (delta 185), reused 86 (delta 69)
> > remote: Sending notification emails to: address@hidden
> > remote: *** Error while generating commit email
> > remote: ***  - mail sending aborted.
> > remote: Traceback (most recent call last):
> > remote:   File "hooks/post-receive", line 62, in <module>
> > remote:     git_multimail.main(sys.argv[1:])
> > remote:   File "/srv/git/emacs.git/hooks/git_multimail.py", line 2631, in 
> > main
> > remote:     run_as_post_receive_hook(environment, mailer)
> > remote:   File "/srv/git/emacs.git/hooks/git_multimail.py", line 2482, in 
> > run_as_post_receive_hook
> > remote:     push.send_emails(mailer, body_filter=environment.filter_body)
> > remote:   File "/srv/git/emacs.git/hooks/git_multimail.py", line 2462, in 
> > send_emails
> > remote:     rev.recipients,
> > remote:   File "/srv/git/emacs.git/hooks/git_multimail.py", line 1472, in 
> > send
> > remote:     p.terminate()
> > remote:   File "/usr/lib/python2.6/subprocess.py", line 1269, in terminate
> > remote:     self.send_signal(signal.SIGTERM)
> > remote:   File "/usr/lib/python2.6/subprocess.py", line 1264, in send_signal
> > remote:     os.kill(self.pid, sig)
> > remote: OSError: [Errno 1] Operation not permitted
> > To address@hidden:/srv/git/emacs.git
> >    6a31219..39372e1  tmp -> concurrency

Since these are messages from "remote", the problem is on Savannah.
So it's pointless to report this here; instead, please report this to
address@hidden

> It might’ve been a pretty large message, as this was merging over two years’ 
> worth of changes from master to the concurrency branch. If that’s the 
> problem, then just saying “sorry, it’s just too darn big” would’ve been much 
> friendlier. :-)

From the traffic on the emacs-diffs mailing list, the mail messages
about this seemed to have been sent successfully, so I'm not sure what
was this about.

> Around the same time, on a different machine, “git remote update” got a 
> “Connection reset by peer” error. A later attempt worked fine.

Maybe this is indeed the cause.