Thanks. Another option in these cases is to mark the test TODO and gracefully ignore it's failure, but this fix is fine in the interim.
On Oct 15, 2016 10:35 AM, "Yann Ylavic" <ylavic....@gmail.com> wrote: > On Sat, Oct 15, 2016 at 4:30 PM, Yann Ylavic <ylavic....@gmail.com> wrote: > > On Sat, Oct 15, 2016 at 4:20 PM, Yann Ylavic <ylavic....@gmail.com> > wrote: > >> On Sat, Oct 15, 2016 at 3:10 PM, Jim Jagielski <j...@jagunet.com> wrote: > >>> Anyone...? Any ideas?? > >> > >> This seems to come from r1756746, which I think should be trunk > >> specific (for now). > > > > The attached works for me.. > > Applied in r1765085. >
