[Scylla-5.2] `should_call_onAdd_with_bootstrap_stop_start` test started failing using `3.11.5.2` and `3.11.4.0` versions

[vponomaryov]

Running the scylla-5.2/driver-tests/java-driver-matrix-test#38 CI job the should_call_onAdd_with_bootstrap_stop_start test failed using 3.11.5.2 and 3.11.4.0 versions:

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.

[vponomaryov]

@fruch is it correct place to file this bug? Or java-driver repo should have been used for it?

[fruch]

@fruch is it correct place to file this bug? Or java-driver repo should have been used for it?

Since it seems to be an issue with our fork versions, it should be reported on java-driver

Also from the sounds of it it might even be a scylla regression

[vponomaryov]

@fruch is it correct place to file this bug? Or java-driver repo should have been used for it?

Since it seems to be an issue with our fork versions, it should be reported on java-driver

Also from the sounds of it it might even be a scylla regression

Created it there: scylladb/java-driver#292