Skip to content

Skip flaky test: test_should_write_successfully_on_leader_switch_using_tx_function #905

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

Conversation

bigmontz
Copy link
Contributor

This test fails because of Javascript driver doesn't validate the tx before send it to the tx function.

In this case, the transaction could be in a failed state when tx.run get called and it produces the
DriverError : : Cannot run query in this transaction, because it has been rolled back either because of an error or explicit termination. (N/A).

This errant behaviour of the driver was fixed in the 5.0 with the TransactionPromise.

…g_tx_function

This test fails because of Javascript driver doesn't validate the tx before send it to the tx function.

In this case, the transaction could be in a failed state when `tx.run` get called and it produces the
`DriverError :  : Cannot run query in this transaction, because it has been rolled back either because of an error or explicit termination. (N/A)`.

This errant behaviour of the driver was fixed in the 5.0 with the TransactionPromise.
@bigmontz bigmontz merged commit 54e3f92 into neo4j:4.4 Mar 25, 2022
@bigmontz bigmontz deleted the 4.4-flacky-test_should_write_successfully_on_leader_switch_using_tx_function branch March 25, 2022 09:02
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

Successfully merging this pull request may close these issues.

1 participant