libev-4.27 timeout not being respected?

[Samuel Williams]

Okay - on the timeout issue, after investigating, I found it was a bug with
our local modifications to libev. It's fixed now, and the issue has gone
away.

Regarding the warnings, there are still a lot of them. Maybe worth a casual
glance to see if anything worth fixing.

Kind regards,
Samuel

On Wed, 28 Aug 2019 at 10:30, Samuel Williams <
space.ship.traveller at gmail.com> wrote:

> We noticed some regressions in timeout handling in libev-4.27 vs 4.25
>
> I am just starting to investigate, but I thought I'd start a discussion
> here too.
>
> In addition, some changes to the source code are generating a lot of
> warnings. You can see the test failures and warnings here:
>
> https://travis-ci.org/socketry/nio4r/jobs/577582532
>
> Kind regards,
> Samuel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schmorp.de/pipermail/libev/attachments/20190828/5adaf5bb/attachment.htm>