Skip to content

Conversation

@panchenko
Copy link
Contributor

No description provided.

@ejona86 ejona86 added the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Aug 25, 2025
@grpc-kokoro grpc-kokoro removed the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Aug 25, 2025
@ejona86 ejona86 added the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Aug 25, 2025
@grpc-kokoro grpc-kokoro removed the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Aug 25, 2025
@ejona86
Copy link
Member

ejona86 commented Aug 27, 2025

One of the recent servlet changes has made the Windows CI heavily flaky. I had retried the Windows CI 4-ish times and it failed for all of them.

It's producing an INTERNAL error. I've sent out #12317 to get a better view of what error is occurring.

@ejona86
Copy link
Member

ejona86 commented Aug 28, 2025

#12317 humorously succeeded the first time. After re-running to get the CI to fail, I was able to see the error for tomcat10Test's TomcatInteropTest.timeoutOnSleepingServer:

Status{code=INTERNAL, description=Received unexpected EOS on empty DATA frame from server, cause=null}

@ejona86 ejona86 merged commit afef4fe into grpc:master Aug 28, 2025
14 of 16 checks passed
AgraVator pushed a commit to AgraVator/grpc-java that referenced this pull request Sep 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants