Grig Gheorghiu schrieb:
> Here are the steps that led to the unit test failures, after your
> checkin of configure and configure.in.
>
> svn update:
> http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%20trunk/builds/55/step-svn/0
>
> configure:
> http://www.python.org/dev/b
On 10/20/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Grig Gheorghiu schrieb:
> >> > Maybe the makefiles should be modified so that a full rebuild is
> >> > triggered when the configure and configure.in files are changed?
> >>
> >> The makefiles already do that: if configure changes, a plain
Grig Gheorghiu schrieb:
>> > Maybe the makefiles should be modified so that a full rebuild is
>> > triggered when the configure and configure.in files are changed?
>>
>> The makefiles already do that: if configure changes, a plain
>> "make" will first re-run configure.
>
> Well, that didn't trigge
On 10/19/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Grig Gheorghiu schrieb:
> > OK, I deleted the checkout directory on one of my buidslaves and
> > re-ran the build steps. The tests passed. So my conclusion is that a
> > full rebuild is needed for the tests to pass after the last checkins
Grig Gheorghiu schrieb:
> OK, I deleted the checkout directory on one of my buidslaves and
> re-ran the build steps. The tests passed. So my conclusion is that a
> full rebuild is needed for the tests to pass after the last checkins
> (which included files such as configure and configure.in).
Inde
On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>>> On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]
> wrote:> > On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:> > >> > > Possibly. If you look at the reason those tests failed it is beca
On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
>
> On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
> > On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > >
> > > Possibly. If you look at the reason those tests failed it is because
> > > time.strftime is missing for some odd re
On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>> Possibly. If you look at the reason those tests failed it is because> time.strftime is missing for some odd reason. But none of recent checkins
> seem to have anything to do with the 'tim
On 10/19/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> Possibly. If you look at the reason those tests failed it is because
> time.strftime is missing for some odd reason. But none of recent checkins
> seem to have anything to do with the 'time' module, let alone with how
> methods are added to
On 10/19/06, Grig Gheorghiu <[EMAIL PROTECTED]
> wrote:
The latest trunk checkin caused almost all Pybots to fail when runningthe Python unit tests.273 tests OK.12 tests failed:test___all__ test_calendar test_capi test_datetime test_emailtest_email_renamed test_imaplib test_mailbox test_str
The latest trunk checkin caused almost all Pybots to fail when running
the Python unit tests.
273 tests OK.
12 tests failed:
test___all__ test_calendar test_capi test_datetime test_email
test_email_renamed test_imaplib test_mailbox test_strftime
test_strptime test_time test_xmlrpc
Her
11 matches
Mail list logo
