Skip to content
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

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

Open
vponomaryov opened this issue Apr 26, 2024 · 4 comments
Assignees

Comments

@vponomaryov
Copy link

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:
Screenshot from 2024-04-22 13-53-10

This test doesn't fail using master scylla in latest runs.

@k0machi
Copy link

k0machi commented May 5, 2024

Unable to reproduce the issue locally - test succeds both on the unstable archive provided and the previous version - maybe test itself is flaky?

@vponomaryov
Copy link
Author

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?

@k0machi
Copy link

k0machi commented May 9, 2024

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.

@vponomaryov
Copy link
Author

Reproduced once again: scylla-5.2/driver-tests/java-driver-matrix-test#40

@roydahan roydahan assigned Bouncheck and unassigned k0machi Jun 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants