[Dmitry Vasiliev]
Sure, but my reasonable assumption was that when you insert an exception
message in a doctest you reread it another one time and fix typos if any.
Relying on ideal behavior is rarely a reasonable assumption ;-)
What actually happens is that people write new doctests, run
Tim Peters wrote:
[Dmitry Vasiliev]
Oops, my bad. I couldn't imagine that misspelled text could been used in
any doctests so I had omitted the testing phase because I was in some
hurry. :-( And unfortunately I was far from any computers for past few
days.
Thanks for following up -- I was
Dmitry Vasiliev wrote:
Sure, but my reasonable assumption was that when you insert an exception
message in a doctest you reread it another one time and fix typos if
any. I'll be more careful in the future about such assumptions.
Without meaning to sound condescending (which certainly is
Tim Peters wrote:
[Jens Vagelpohl]
Running the tests on the current ZODB trunk using a self.built
Python 2.4.2 on OS X (10.4.3) the following test fails:
They fail the same way on my Windows box and a random Linux box today ...
OK, Dmitry, you fixed the spelling (replaced onnection with
[Dmitry Vasiliev]
Oops, my bad. I couldn't imagine that misspelled text could been used in
any doctests so I had omitted the testing phase because I was in some
hurry. :-( And unfortunately I was far from any computers for past few
days.
Thanks for following up -- I was afraid you had
Tim Peters wrote:
[Jens Vagelpohl]
Just as a heads-up because I don't know how much testing ever gets done
on OS X:
I do: none ;-)
Can someone volunteer to run a Mac OS X buildbot slave? If not,
I'll try to set up an *old* iMac that the PSF seems to have
abandoned at ZC. :)
For ZODB
On 11 Dec 2005, at 16:35, Jim Fulton wrote:
Tim Peters wrote:
[Jens Vagelpohl]
Just as a heads-up because I don't know how much testing ever
gets done
on OS X:
I do: none ;-)
Can someone volunteer to run a Mac OS X buildbot slave? If not,
I'll try to set up an *old* iMac that the PSF
Jim Fulton wrote:
I'll update the buildbot setups to run all tests.
That would be a good interim solution; long term I'd like to get
dedicated ZODB buildbot slaves so they can be set up to react to check
ins to ZODB, instead of coincidentally being run when Zope is changed.
I'll add that to
[Jim Fulton]
...
Tim. we should set up a buildbot whachamajiggy (I have trouble keeping
the buildbot jargon straight) to run ZODB tests on checkin, so we can
catch these sorts of things sooner.
Happy to help, and it's certainly the right thing to do, but don't know
anything about setting up
Jim Fulton wrote:
Tim Peters wrote:
...
to stop running ZODB tests, no version of ZODB is regularly tested on any
platform anymore; the overnight test runners and buildbot.zope.com
used to
at least test some ZODB versions regularly
Yes, very specific versions, which doesn't help catch
[Tim]
... the overnight test runners and buildbot.zope.com used to at
least test some ZODB versions regularly
{Jim]
Yes, very specific versions, which doesn't help catch bugs on the trunk
or even on a branch.
Yes; I said that later myself. Note that the overnight test runners are
still
[Jens Vagelpohl]
Just as a heads-up because I don't know how much testing ever gets done
on OS X:
I do: none ;-) For ZODB specifically, since the Zope trunks were changed
to stop running ZODB tests, no version of ZODB is regularly tested on any
platform anymore; the overnight test runners and
12 matches
Mail list logo
