uschindler commented on PR #14457:
URL: https://github.com/apache/lucene/pull/14457#issuecomment-2792091824
I sit enough to only change that part so it affects all NRT tests?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
uschindler commented on PR #14457:
URL: https://github.com/apache/lucene/pull/14457#issuecomment-2792554897
> > Is it enough to only change that part so it affects all NRT tests?
>
> Yes, this is the only place creating Sockets there. Also, I didn't touch
any ServerSocket as that's di
rmuir commented on PR #14457:
URL: https://github.com/apache/lucene/pull/14457#issuecomment-2792564423
Yeah, we can look into it separately. It is different and is timeout for
`accept()` calls only IIRC. I haven't looked at the way these tests manage
connections, but it is not implicated in
rmuir merged PR #14457:
URL: https://github.com/apache/lucene/pull/14457
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apach
rmuir commented on PR #14457:
URL: https://github.com/apache/lucene/pull/14457#issuecomment-2792522271
> Is it enough to only change that part so it affects all NRT tests?
Yes, this is the only place creating Sockets there.
Also, I didn't touch any ServerSocket as that's different a
rmuir opened a new pull request, #14457:
URL: https://github.com/apache/lucene/pull/14457
These nightly tests sometimes hang and are killed by timeout, instead of
passing or failing. Upon inspection of one of the failures, the hung thread is
stuck in `SocketDispatcher.read0()` native code,
