-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TableServiceAsyncTest timeout unit test failure #4798
Comments
Closed
devinrsmith
added a commit
to devinrsmith/deephaven-core
that referenced
this issue
Nov 9, 2023
This is in support of deephaven#4798. While this _is_ a fix to BatchHandler logic, it isn't the underlying cause of 4798. Next time 4798 is triggered in CI though, we should have more details to go off of.
I've done 8 CI runs and so far have been unable to reproduce this issue. After #4802 merges, if this issues triggers in CI again we should have much more details to go off of. |
devinrsmith
added a commit
to devinrsmith/deephaven-core
that referenced
this issue
Nov 9, 2023
Potential fix for deephaven#4798
devinrsmith
added a commit
that referenced
this issue
Nov 9, 2023
This is in support of #4798. This adds some additional logic to BatchHandler to improve logging in exceptional cases. This also fixes some exceptional cases in TableServiceAsyncImpl. I _expected_ this fixes the intermittent test failures.
I think #4802 fixes this - leaving open for a week to see if we here anymore cases. |
devinrsmith
changed the title
TableServiceAsyncTest longChainAsyncExportOnlyLast unit test failure
TableServiceAsyncTest timeout unit test failure
Nov 10, 2023
Updated comment to specifically make sure this is about the timeout nature of this issue. |
stanbrub
pushed a commit
that referenced
this issue
Nov 15, 2023
This is in support of #4798. This adds some additional logic to BatchHandler to improve logging in exceptional cases. This also fixes some exceptional cases in TableServiceAsyncImpl. I _expected_ this fixes the intermittent test failures.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that the following test is sometimes failing:
It suggests that there is an underlying race (potentially Batch / ETCR or related), or client implementation bug; but it's possible the timeout is too short given CI resources, TBD.
The text was updated successfully, but these errors were encountered: