[Neal Norwitz]
> ...
> I also think I know how to do the "double builds" (one release and one
> debug). But it's too late for me to change it tonight without
> screwing it up.
I'm not mad :-). The debug build is more fruitful than the release
build for finding problems, so doing two debug-build
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> Tim Peters wrote:
>> Speaking of which, a number of test failures over the past few weeks
>> were provoked here only under -r (run tests in random order) or under
>> a debug build, and didn't look like those were specific to Windows.
>> Adding -r to
On 2/21/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
>
> I agree with this, but don't know a clean way to do 2 builds. I
> modified buildbot to:
>
> - Stop doing the second "without deleting .py[co]" run.
> - Do one run with a debug build.
> - Use -uall -r for both.
I screwed it up, so now it d
On 2/21/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Neal> IMO compiler warnings should generate emails from buildbot.
> >
> > It doesn't generate emails for any other condition. I think it should just
> > turn the compilation section yellow.
>
> It would be
On 2/21/06, Tim Peters <[EMAIL PROTECTED]> wrote:
>
> Since the most fruitful variations (IME) for finding code errors are
> using -r and running a debug build too, I'd change the current
> run-all-the-time recipes to:
>
> - Stop doing the second "without deleting .py[co]" run.
> - Do one run with
Martin> So for multiplying this by 8, I would have to create 48 lines of
Martin> Apache configuration, and use 24 TCP ports. This can be done,
Martin> but it would take some time to implement.
I'm not too worried about that because it's a one-time cost. I'd be willing
to help out. J
>> Let me rephrase that. I assume the people digging through Py_ssize_t
>> issues have been looking at compilation warnings for platforms other
>> than Mac OSX.
Martin> In the buildbot log, I see only a single one of these, and only
Martin> in an OSX-specific module. So no -
[Martin v. Löwis]
> So what is your recipe:
I don't have one. I personally always use -uall and -r, and then run
the tests 8 times, w/ and w/o -O, under debug and release builds, and
w/ and w/o deleting .py[co] files first. Because that last one almost
never finds problems anymore, perhaps it wo
Martin v. Löwis wrote:
> [EMAIL PROTECTED] wrote:
[...]
>
> So for multiplying this by 8, I would have to create 48 lines of
> Apache configuration, and use 24 TCP ports. This can be done, but
> it would take some time to implement. And who is going to look
> at the 24 pages?
This last point is t
[EMAIL PROTECTED] wrote:
> Now that you've broken the buildbot page into two (trunk and 2.4) I assume
> breaking it down even further wouldn't be a major undertaking. If we can
> recruit a suitable number of boxes I see no particular reason you can't
> support a 2x, 4x, 8x or more increase in the
Martin> So what is your recipe: Add -r to all buildbots? Only to those
Martin> which have an 'a' in their name? Only to every third build?
Martin> Duplicating the number of builders?
Martin> Same question for --with-pydebug. Combining this with -r would
Martin> multiply the nu
Terry Reedy wrote:
> "Neal Norwitz" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
>>There's nothing to prevent buildbot from making debug builds, though
>>that is not currently done.
>
>
> Now that there are separate report pages for 2.4 and 2.5, you could add
> pages for deb
[EMAIL PROTECTED] wrote:
> Neal> IMO compiler warnings should generate emails from buildbot.
>
> It doesn't generate emails for any other condition. I think it should just
> turn the compilation section yellow.
It would be easy to run the builds with -Werror, making warnings let the
compil
[EMAIL PROTECTED] wrote:
> Ronald> How many of those do you see when you ignore the warnings you
> Ronald> get while building the Carbon extensions?
>
> skip> I see a bunch related to Py_ssize_t. Those have nothing to do
> skip> with Carbon. I don't see them on the gentoo build,
Neal Norwitz wrote:
>>How many of those do you see when you ignore the warnings you get
>>while building the Carbon extensions? Those extensions wrap loads of
>>deprecated functions, each of which will give a warning.
>
>
> RIght:
> http://www.python.org/dev/buildbot/all/g4%20osx.4%20trunk/builds
Tim Peters wrote:
> Speaking of which, a number of test failures over the past few weeks
> were provoked here only under -r (run tests in random order) or under
> a debug build, and didn't look like those were specific to Windows.
> Adding -r to the buildbot test recipe is a decent idea. Getting
"Neal Norwitz" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> There's nothing to prevent buildbot from making debug builds, though
> that is not currently done.
Now that there are separate report pages for 2.4 and 2.5, you could add
pages for debug builds, perhaps with a lower fr
Ronald> How many of those do you see when you ignore the warnings you
Ronald> get while building the Carbon extensions?
skip> I see a bunch related to Py_ssize_t. Those have nothing to do
skip> with Carbon. I don't see them on the gentoo build, so I assume
skip> they just ha
>> Unfortunately, there are a ton of warnings on OS X right now.
Ronald> How many of those do you see when you ignore the warnings you
Ronald> get while building the Carbon extensions?
I see a bunch related to Py_ssize_t. Those have nothing to do with Carbon.
I don't see them on th
Neal> IMO compiler warnings should generate emails from buildbot.
It doesn't generate emails for any other condition. I think it should just
turn the compilation section yellow.
Skip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.
On 21-feb-2006, at 10:19, Neal Norwitz wrote:
> On 2/21/06, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>>
>> On 21-feb-2006, at 9:09, Neal Norwitz wrote:
>>
>>> Unfortunately, there are a ton of
>>> warnings on OS X right now.
>>
>> How many of those do you see when you ignore the warnings you ge
On 2/21/06, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>
> On 21-feb-2006, at 9:09, Neal Norwitz wrote:
>
> > Unfortunately, there are a ton of
> > warnings on OS X right now.
>
> How many of those do you see when you ignore the warnings you get
> while building the Carbon extensions? Those extensi
On 21-feb-2006, at 9:09, Neal Norwitz wrote:
> Unfortunately, there are a ton of
> warnings on OS X right now.
How many of those do you see when you ignore the warnings you get
while building the Carbon extensions? Those extensions wrap loads of
deprecated functions, each of which will give a w
On 2/20/06, Tim Peters <[EMAIL PROTECTED]> wrote:
>
> Speaking as a PSF director, I might not vote for that :-) Fact is
> I've been keeping the build & tests 100% healthy on WinXP Pro, and
> that requires more than just running the tests (it also requires
> repairing compiler warnings and Unixisms
[Aahz]
> If you're willing to commit to running a buildbot, and the only thing
> preventing you is shelling out $$$ to Microsoft, send me e-mail. I'll
> compile a list to send to the PSF and we'll either poke Microsoft to
> provide some more free licenses or pay for it ourselves. This is what
> t
If you're willing to commit to running a buildbot, and the only thing
preventing you is shelling out $$$ to Microsoft, send me e-mail. I'll
compile a list to send to the PSF and we'll either poke Microsoft to
provide some more free licenses or pay for it ourselves. This is what
the PSF is for!
N
26 matches
Mail list logo
