Skip to content

RemoteOperations::exec_command must not raise an exception when 'expect_error' is True (#159) #160

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

dmitry-lipetsk
Copy link
Collaborator

This PR does two things:

test_local.py contains set of test for LocalOperations
 - test_exec_command_success
 - test_exec_command_failure
 - test_exec_command_failure__expect_error

Changes in TestRemoteOperations:
 - test_exec_command_failure exptects an exception
 - new test test_exec_command_failure__expect_error was added

TestRemoteOperations::test_exec_command_failure__expect_error will fail because RemoteOperations::exec_command does not handle the 'expect_error' parameter correctly.
Dmitry Kovalenko and others added 2 commits December 8, 2024 00:12
RunConditions contains the code to check the execution condition of tests.

It is used in TestLocalOperations.
@dmitry-lipetsk
Copy link
Collaborator Author

Patch was tested internal test for probackup2 - all is ok.

RemoteOperations is used only in MultihostCatchupTest - this test was passed without errors.

@dmitry-lipetsk dmitry-lipetsk merged commit 1c73113 into postgrespro:master Dec 8, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant