Bug summary
__
Summary for 2011-10-30 through 2011-11-06
Opened Closed Total Change
Enhancements: 11 6770 +5
Defects: 13 4519 +9
Tasks: 2 0 7
> > Then, baseline. I've run the trial using select reactor in the
> > expectation of finding all tests passed.
> >
> > This is not the case, there are a couple of failed ones. Those are
> > also failed with the kqueue reactor, so I need to know whether I need
> > to inspect those or those are prob
On Sat, 2011-11-05 at 04:48 -0700, Tobias Oberstein wrote:
> Then, whats the difference between FAIL and ERROR?
Fail means an assertion failed. Error means an unexpected exception was
throwhn.
> Then, there are a couple of tests which are skipped because
>
> xxx_KQueueReactor
> No module named k
> We've said e.g. Windows only supports Python 2.5 or later even when
> everything else supports Python 2.4. And we have inlineCallbacks which only
> runs on Python 2.5 or later. Saying "kqueue reactor only works on Python 2.6
> and later" seems fine to me.
For completeness: there seem to be 2 pac
> > if there is anything I can do to clarify (like i.e. running on
> > non-virtualized
> hardware FreeBSD) let me know.
>
> Have you run the tests on OS X as well?
I'll do that.
> > Caveat: as attached to the ticket, there are some errs when running
> > trial which don't happen with select reac
