On Fri, 17 Jun 2016, 'Jay Grizzard' via memcached wrote:

> Also, OSX consistently gives:
>       t/issue_70.t ......... 1/4
> #   Failed test at t/issue_70.t line 22.
> #          got: 'SERVER_ERROR object too large for cache
> # '
> #     expected: 'CLIENT_ERROR bad command line format
> # '
> # Looks like you failed 1 test of 4.
> t/issue_70.t ......... Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/4 subtests
>
>
> (I haven’t really gotten a chance to look deeper)

Any chance you could bisect that one? would much appreciate, I don't have
access to OS X.

> I’ll do some testing on RHEL 5 6 & 7 a little later, just to sanity check 
> there.

Thanks!

> No idle kicker patch this release? :(

Release got too large. I'm going to do the next round of PR's and issues
next week. Should be a short release cycle for a little while at least :)

> -j
>
> On Fri, Jun 17, 2016 at 12:50 PM, dormando <dorma...@rydia.net> wrote:
>
>
>       On Fri, 17 Jun 2016, Dagobert Michelsen wrote:
>
>       > Hi Dormando,
>       >
>       > Am 17.06.2016 um 10:39 schrieb dormando <dorma...@rydia.net>:
>       > > https://github.com/memcached/memcached/pull/127 is now "done", as 
> much as
>       > > it'll be done for this release. More work in future releases.
>       > >
>       > > I've already pulled the next branch into master. I'll be cutting 
> this in
>       > > the morning unless someone has a major problem with it between now 
> and
>       > > then :)
>       >
>       > Not a major problem, but the testsuite on Solaris x86 on 32 and 64 
> bit has issues:
>       >   https://buildfarm.opencsw.org/buildbot/waterfall?category=memcached
>       >
>       > > #   Failed test 'canary ==
>       > > BBB...
>       > > #   at 
> /export/home/buildbot/slave/memcached-solaris10-i386/build/t/lib/MemcachedTest.pm
>  line 59.
>       > > #          got: 'END
>       > > # '
>       > > #     expected: 'VALUE canary 0 66560
>       > > # BBB...
>       > > # END
>       > > # '
>       > >
>       > > # Looks like you failed 1 test of 224.
>
>       Thanks! I saw that bouncing around while I was filling up 'next'. 
> there's
>       a flaky test I've punted to the next release to work on. I was able to 
> get
>       it to fail rarely locally. it does seem to fail more often on your
>       buildbot.
>
>       --
>
>       ---
>       You received this message because you are subscribed to the Google 
> Groups "memcached" group.
>       To unsubscribe from this group and stop receiving emails from it, send 
> an email to memcached+unsubscr...@googlegroups.com.
>       For more options, visit https://groups.google.com/d/optout.
>
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "memcached" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to memcached+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to memcached+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to