-
Notifications
You must be signed in to change notification settings - Fork 72
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
Test Failure: read_only_trxs/with_3_read_only_threads_no_tierup is stuck #1815
Labels
👍 lgtm
OCI
Work exclusive to OCI team
test-instability
tag issues for flaky tests, high priority to address
Milestone
Comments
linh2931
added
the
test-instability
tag issues for flaky tests, high priority to address
label
Oct 24, 2023
heifner
added a commit
that referenced
this issue
Oct 24, 2023
heifner
added a commit
that referenced
this issue
Oct 24, 2023
heifner
added a commit
that referenced
this issue
Oct 24, 2023
[5.0] Test Fix: Avoid deadlock on app_thread
heifner
added a commit
that referenced
this issue
Oct 24, 2023
heifner
added a commit
that referenced
this issue
Oct 24, 2023
heifner
added a commit
that referenced
this issue
Oct 24, 2023
[5.0 -> main] Test Fix: Avoid deadlock on app_thread
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
👍 lgtm
OCI
Work exclusive to OCI team
test-instability
tag issues for flaky tests, high priority to address
While running
plugin_test
to try to reproduce the problem in #1794, I sawplugin_test
was stuck inread_only_trxs/with_3_read_only_threads_no_tierup
and eventually timed out after 1500 seconds.The test calls
activate_protocol_features_set_bios_contract
which in turns callsset_code
. Theset_code
fails due to exceedingmax_transaction-time
(10000us).There are two issues here
max_transaction-time
is set too short.set_code
should not get stuck even if it fails to set code. Need to investigate further why it is stuck in failure.The text was updated successfully, but these errors were encountered: