You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Test] BaseTck hard-coded 25 ms timeout is flaky on slower machines #8378
Using Temurin and Zulu 26.0.2.1, Gradle 9.9.0, on Windows, full testNG runs produced varying failures such as:
FlowableVirtualTransformVirtual2TckTest.optional_spec104_mustSignalOnErrorWhenFails: publisher did not call onError within 25 ms.
FlowableVirtualTransformVirtual2TckTest.required_spec317_mustSupportACumulativePendingElementCountUpToLongMaxValue: did not receive expected element or completion within 25 ms.
FlowableVirtualTransformVirtual2TckTest.required_spec317_mustSupportAPendingElementCountUpToLongMaxValue: did not receive expected element or completion within 25 ms.
FlowableVirtualCreateVirtualTckTest.required_spec102_maySignalLessThanRequestedAndTerminateSubscription: did not receive expected element or completion within 25 ms.
Across different full runs, 8, 3, and 1 TCK tests failed. The affected TCK classes passed when rerun independently, indicating timing sensitivity rather than a stable functional regression.
The current 4.x file matches the unmodified original used for these runs.
Suggested direction
Please consider making the TCK timeout configurable (for example, through a system property or environment variable), so the default can remain 25 ms while local development and slower CI workers can use a more suitable value.
AI disclosure: Kimi Code assisted with reproducing and analyzing the timing failures and drafting this report. No production-code patch is attached.
Activity
akarnokd commentedon Nov 17, 2026
There is the
BaseTCK(long timeout)constructor, you can have those tests override the default with 50 and see if that helps locally.