Re: [Infrastructure-staff] Errors when pushing to hg.python.org/jython

Thanks Ernest!

First observed for me last night: Mon, 25 Sep 2017 about 21:00 +0100, 
but I haven't pushed for about 4 weeks (been working in a forked repo). 
I started this thread almost immediately after the merge and push 
(https://hg.python.org/jython/rev/50393fac6f20).

My push 4 weeks ago (/Sun Aug 27 07:45:40 EDT 2017/) is the last thing 
on the archive 
https://mail.python.org/pipermail/jython-checkins/2017-August/date.html 
and I remember no such an error.

Since Jim says  "I have also seen this error.  ..." I assume that would 
have been when pushing soon after Sat, 09 Sep 2017 14:02:01 -0600 
(https://hg.python.org/jython/rev/8d52ad2559f5). However, he could be 
more precise.

So on or after 27 Aug and (maybe) before 10 Sep?

Jeff


On 26/09/2017 00:49, Ernest W. Durbin III wrote:
> Hey!
>
> Ernest here! I’m one of the volunteers on the PSF infra staff.
>
> Yeah it is fair to say that the mercurial installation has not gotten 
> much love since the core python workflows moved to GitHub.
> But we also haven’t heard any complaints until now.
>
> I’m AFK right now but will be able to spend some time trying to help 
> in the morning.
>
> Was this a recent failure for y’all or has it been ongoing? Knowing 
> when it went goofy will be a big help!
>
> -Ernest
>
> On September 25, 2017 at 6:13:46 PM, Jeff Allen ([email protected] 
> <mailto:[email protected]>) wrote:
>
>> Or administered on the assumption everyone has moved Git. 
>> https://hg.python.org/?sort=lastchange
>>
>> I think this (fairly obviously) is the hook that sends e-mail, but 
>> why the call has changed I can't guess.
>>
>> I'm happy to move to GitHub. Start with the CPython dev guide as it 
>> contains a well thought-out way of working? (I keep meaning to.)
>>
>> Jeff
>>
>>
>> On 25/09/2017 21:40, Jim Baker wrote:
>>> I have also seen this error. I assume that a post-commit hook is 
>>> being run on the hg server, and it is failing. Not good.
>>>
>>> This message may be implicitly telling us we need to get off 
>>> hg.python.org <http://hg.python.org> sooner than later, since it's 
>>> no longer being as actively administered. (Perhaps not at all in fact.)
>>>
>>> On Mon, Sep 25, 2017 at 2:35 PM, Stefan Richthofer 
>>> <[email protected] <mailto:[email protected]>> wrote:
>>>
>>>     Also observed these errors and additionally I did not receive an
>>>     email notification from jython-checkins.
>>>     Not that I cared too much for the email notification (still nice
>>>     to have), but I suspect the issues could be
>>>     related. Or did you receive email notification for recent pushes?
>>>     *Gesendet:* Montag, 25. September 2017 um 22:20 Uhr
>>>     *Von:* "Jeff Allen" <[email protected] <mailto:[email protected]>>
>>>     *An:* "Jython Developers" <[email protected]
>>>     <mailto:[email protected]>>,
>>>     [email protected]
>>>     <mailto:[email protected]>
>>>     *Betreff:* [Jython-dev] Errors when pushing to
>>>     hg.python.org/jython <http://hg.python.org/jython>
>>>
>>>     Just now got these error messages, actually 4 repeats, one for
>>>     each change set:
>>>
>>>     PS jython-int> hg push
>>>     pushing to ssh://[email protected]/jython
>>>     <mailto:ssh://[email protected]/jython>
>>>     searching for changes
>>>     remote: adding changesets
>>>     remote: adding manifests
>>>     remote: adding file changes
>>>     remote: added 4 changesets with 28 changes to 25 files
>>>     remote: Traceback (most recent call last):
>>>     remote:   File "/srv/hg/repos/hooks/mail.py", line 166, in incoming
>>>     remote:     return _incoming(ui, repo, **kwargs)
>>>     remote:   File "/srv/hg/repos/hooks/mail.py", line 102, in _incoming
>>>     remote:     diffstat = patch.diffstat(iterlines(diffchunks),
>>>     width=60, git=True)
>>>     remote: TypeError: diffstat() got an unexpected keyword argument
>>>     'git'
>>>     remote: error: incoming.notify hook raised an exception:
>>>     diffstat() got an unexpected keyword argument 'git'
>>>     remote: (run with --traceback for stack trace)
>>>
>>>     ... and 3 more the same (from "remote: Traceback ...").
>>>
>>>     It seems to have worked (my change sets landed), but something's
>>>     not right at the PSF end. Any ideas?
>>>
>>>     Jeff
>>>
>>>     ------------------------------------------------------------------------------
>>>     Check out the vibrant tech community on one of the world's most
>>>     engaging tech sites, Slashdot.org!
>>>     http://sdm.link/slashdot_______________________________________________
>>>     <http://sdm.link/slashdot_______________________________________________>
>>>     Jython-dev mailing list [email protected]
>>>     <mailto:[email protected]>
>>>     https://lists.sourceforge.net/lists/listinfo/jython-dev
>>>     <https://lists.sourceforge.net/lists/listinfo/jython-dev>
>>>
>>>     ------------------------------------------------------------------------------
>>>     Check out the vibrant tech community on one of the world's most
>>>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>     _______________________________________________
>>>     Jython-dev mailing list
>>>     [email protected]
>>>     <mailto:[email protected]>
>>>     https://lists.sourceforge.net/lists/listinfo/jython-dev
>>>     <https://lists.sourceforge.net/lists/listinfo/jython-dev>
>>>
>>>
>>
>> _______________________________________________
>> Infrastructure-staff mailing list
>> [email protected] <mailto:[email protected]>
>> https://mail.python.org/mailman/listinfo/infrastructure-staff

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev