Paul Moore writes:
> Do you run your slave as a service? (And for that matter, what do
> other Windows slave owners do?) Are there any "best practices" for
> ongoing admin of a Windows buildslave that might be worth collecting
> together? (I'll try to put some notes on what I've found together -
Am 14.11.2010 19:35, schrieb Antoine Pitrou:
> On Sun, 14 Nov 2010 19:27:22 +0100
> "Martin v. Löwis" wrote:
>> > I suspect my hg-fu is inadequate to at this point - I get an 'access
>> > to repository "hg.python.org/hooks" not permitted' error when I try to
>> > push the modified file to "ssh://h
Nick Coghlan gmail.com> writes:
> of the exception information. logging could also gain an independent
> "stack_trace=True" option to request inclusion of a stack trace
> independently of whether or not exception information is included.
Good point, Nick. There are times when you'd want to know
>> I think this is something that needs to be fixed: I fail to see the
>> point of having this extra repos/ directory in the path (even though
>> it's certainly useful to have them all in a separate directory on disk).
>
> IIUC, "repos/hooks" is interpreted as a relative path to the "hg"
> user's
On Sun, 14 Nov 2010 19:27:22 +0100
"Martin v. Löwis" wrote:
> > I suspect my hg-fu is inadequate to at this point - I get an 'access
> > to repository "hg.python.org/hooks" not permitted' error when I try to
> > push the modified file to "ssh://h...@hg.python.org/hooks".
>
> Try
>
> ssh://h...@h
> I suspect my hg-fu is inadequate to at this point - I get an 'access
> to repository "hg.python.org/hooks" not permitted' error when I try to
> push the modified file to "ssh://h...@hg.python.org/hooks".
Try
ssh://h...@hg.python.org/repos/hooks
I think this is something that needs to be fixed:
On 14 November 2010 02:40, David Bolen wrote:
> There's been a bit of an uptick in the past few weeks with hung
> python_d processes (not a new issue, but it ebbs and flows), so I'm
> going to try to pull together a monitor script this weekend to start
> killing them off automatically. Should at
On 12 November 2010 17:07, Terry Reedy wrote:
> On 11/12/2010 3:44 AM, Paul Moore wrote:
>>
>> Hi,
>> My buildbot has been failing for some time because of these 2 issues,
>> both related to the fact that tests are hanging when run as a service
>> (and hence have no display to open GUI elements on
Am 14.11.2010 13:39, schrieb Nick Coghlan:
> On Sun, Nov 14, 2010 at 8:20 PM, "Martin v. Löwis" wrote:
>> See
>>
>> http://hg.python.org/hooks/
>>
>> You should have push permissions to that repository.
>
> I suspect my hg-fu is inadequate to at this point - I get an 'access
> to repository "hg.p
On Sun, Nov 14, 2010 at 8:20 PM, "Martin v. Löwis" wrote:
> See
>
> http://hg.python.org/hooks/
>
> You should have push permissions to that repository.
I suspect my hg-fu is inadequate to at this point - I get an 'access
to repository "hg.python.org/hooks" not permitted' error when I try to
push
On Sun, Nov 14, 2010 at 8:20 PM, "Martin v. Löwis" wrote:
> Am 14.11.2010 09:25, schrieb Nick Coghlan:
>> On Sun, Nov 14, 2010 at 1:10 PM, Terry Reedy wrote:
>>> Much better except possible for \n after 'summary:'
>>
>> That extra line break helps more for multi-line checkin messages
>> (which ha
On Sun, Nov 14, 2010 at 8:14 PM, "Martin v. Löwis" wrote:
> I'm in favor of deprecating it first.
Aye. I've made the best case I could for keeping it, and even I don't
find it terribly convincing. So deprecation for 3.2 sound like a
reasonable option.
Regards,
Nick.
--
Nick Coghlan | ncogh
On Sun, Nov 14, 2010 at 1:40 PM, R. David Murray wrote:
> Issue 1553375 [1] proposes a patch to add an 'allframes' option to the
> traceback printing and formatting routines so that the full traceback
> from the top of the execution stack down to the exception is printed,
> instead of just from th
"Martin v. Löwis" writes:
> This is what kill_python.exe is supposed to solve. So I recommend to
> investigate why it fails to kill the hanging Pythons.
Yeah, I know, and I can't say I disagree in principle - not sure why
Windows doesn't let the kill in that module work (or if there's an
issue a
Am 14.11.2010 09:25, schrieb Nick Coghlan:
> On Sun, Nov 14, 2010 at 1:10 PM, Terry Reedy wrote:
>> Much better except possible for \n after 'summary:'
>
> That extra line break helps more for multi-line checkin messages
> (which happen reasonably often). Doesn't really bother me either way -
> I
> This is a completely separate issue, though probably around just as
> long, and like the popup problem its frequency changes over time. By
> "hung" here I'm referring to cases where something must go wrong with
> a test and/or its cleanup such that a python_d process remains
> running, usually s
> We should also keep in mind that *Microsoft* have chosen to keep the
> bytes Win32 APIs around, despite their flaws, all in the name of
> backwards compatibility.
Of course, Microsoft is in a different position. If they remove a
functionality in some release, their users typically can't go back
> If the code is currently working and isn't a security hole, then we
> obviously don't "have to".
> Apparently several developers "want to", which is different.
In case the motivation for that isn't clear: it would produce a
significant code reduction, and therefore ease maintenance.
Regards,
Ma
Nick Coghlan writes:
> Do we have any idea why the workaround to avoid the popup windows
> stopped working? (assuming it ever worked reliably - I thought it did,
> but that impression may have been incorrect)
Oh, the pop-up handling for the RTL dialogs still seems to be working
fine (at least I
On Sun, Nov 14, 2010 at 1:10 PM, Terry Reedy wrote:
> Much better except possible for \n after 'summary:'
That extra line break helps more for multi-line checkin messages
(which happen reasonably often). Doesn't really bother me either way -
I'm mainly looking for info on who has the ability to c
On Sun, Nov 14, 2010 at 12:40 PM, David Bolen wrote:
> Antoine Pitrou writes:
>
>> (even though the Windows buildbots give
>> a rather unconventional meaning to the word "stability").
>
> Nag, nag, nag :-)
>
> There's been a bit of an uptick in the past few weeks with hung
> python_d process
21 matches
Mail list logo
