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
should_call_onAdd_with_bootstrap_stop_start
3.11.5.2.com.datastax.driver.core.NodeRefreshDebouncerTest
Wanted but not invoked:
stateListener.onAdd(<Capturing argument>);
-> at com.datastax.driver.core.NodeRefreshDebouncerTest.should_call_onAdd_with_bootstrap_stop_start(NodeRefreshDebouncerTest.java:63)
However, there were other interactions with this mock:
stateListener.onRegister(
com.datastax.driver.core.Cluster@3d65fbab
);
-> at com.datastax.driver.core.Cluster.register(Cluster.java:518)
stateListener.onUp(/127.0.1.2:43329);
-> at com.datastax.driver.core.Cluster$Manager.onUp(Cluster.java:2127)
(Wanted but not invoked)
Screenshot:
This test doesn't fail using master scylla in latest runs.
The text was updated successfully, but these errors were encountered:
Unable to reproduce the issue locally - test succeds both on the unstable archive provided and the previous version - maybe test itself is flaky?
The failure happens using latest 5.2 scylla. Did you try it out?
Yes, I've tried the version that was in the run you've linked, and we also re-ran jenkins job for 5.2 and it seems it didn't fail this time. I think the reason here is that the test has a configured timeout and the instance provided sometimes exceeds it - default value for the timeout is 1 second, haven't yet checked what the driver is built with however.
Running the scylla-5.2/driver-tests/java-driver-matrix-test#38 CI job the
should_call_onAdd_with_bootstrap_stop_start
test failed using3.11.5.2
and3.11.4.0
versions:Screenshot:
This test doesn't fail using
master
scylla in latest runs.The text was updated successfully, but these errors were encountered: