Thomas Heller schrieb:
> Martin v. Löwis schrieb:
>>> Since the tests fail on the trunk (on the windows machines),
>>> the 'clean' step is not run.
>>
>> No. The 'clean' step is run even if the test step failed.
>>
>> The problem must be somewhere else: for some reason, the
>> connection breaks down/times out; this causes the build
>> to abort.
>>
> On the windows buildbot named x86 XP-3 trunk I see:
>
> An XP firewall message box asking if python_d should be unblocked (which is
> possibly unrelated).
>
> A Debug assertion message box. Clicking 'Retry' to debug start Visual Studio,
> it points at line 1343 in db-4.4.20\log\log_put.c:
>
> /*
> * If the open failed for reason other than the file
> * not being there, complain loudly, the wrong user
> * probably started up the application.
> */
> if (ret != ENOENT) {
> __db_err(dbenv,
> "%s: log file unreadable: %s", *namep, db_strerror(ret));
> =>> return (__db_panic(dbenv, ret));
> }
>
> Now that I have written this I'm not so sure any longer whether this was for
> the trunk
> or the py3k build ;-(.
I've checked again: it is in the trunk.
Do you know if it is possible to configure windows so that debug assertions do
NOT
display a message box (it is very convenient for interactive testing, but not so
for automatic tests)?
Thomas
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
