emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Ken Raeburn
Subject: mail-sending error from git server updating "concurrency" branch
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

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. 
:-)

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

Ken


reply via email to

[Prev in Thread] Current Thread [Next in Thread]