Test disabled in swift-corelibs-foundation PR#754.

dgrove-oss (JIRA User) , seabaylea (JIRA User) - I remember the assertion failure reported above was fixed in libkqueue for the URLSession PR. Is the latest libkqueue not being picked up? I am aware of a discussion, on the libdispatch mailing list, around moving away from libkqueue.. but I am unable to join the dots here! Can you please help?

Comment by David Grove (JIRA)

The version of libkqueue we are currently using is a bit old (1873b186 from Sept 23, 2016). I don't think we specifically did anything to fix this assertion failure since then however (as far as I know it is an intermittent failure we have been ignoring).

Once the whole dispatch team gets back from vacation (next week) we can discuss whether it makes sense to update the libkqueue version being used by dispatch. But I don't expect a refresh of the libkqueue to resolve this problem.

If you have a deterministic way to trigger this failure, it might be worth investigating further. Does the test trigger this assertion every time? Previous times this assertion have been triggered have not been repeatable.

IIRC the CI test was failing often or always, but it looks like ci.swift.org was rebooted recently and doesn't have any history for it.

dgrove-oss (JIRA User) - I believe this PR mheily/libkqueue#10 by ianpartridge (JIRA User) did fix the assertion failure.

Comment by David Grove (JIRA)

That pull request is from May; it was merged in June and is included in the version of libkqueue we are currently using.

I am un-assigning myself from this since this is a libkqueue failure and in my understanding we have plans to move to a kqueue-less, epoll-based libdispatch in the near future.

Changing the component to libdispatch. Thanks.

Comment by David Grove (JIRA)

We've removed libkqueue; issue no longer relevant.