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

Require a reason when marking a server bad #654

Merged
merged 1 commit into from
Dec 5, 2023

Conversation

alecharmon
Copy link
Contributor

@alecharmon alecharmon commented Dec 4, 2023

When calling mark_bad require a reason so it can be logged rather than
the generic message. Relates to #648

@levkk
Copy link
Contributor

levkk commented Dec 4, 2023

The change is welcome, let me know when it compiles and passes our test suite, and I'll be happy to review and merge.

When calling mark_bad require a reason so it can be logged rather than
the generic message
@alecharmon
Copy link
Contributor Author

@levkk thanks! I am getting transient test errors on my last couple runs, is there a chance the tests are flaking?

@levkk
Copy link
Contributor

levkk commented Dec 4, 2023

Definitely possible that some tests are flakey. If it fails consisitently though, there is an issue.

@levkk
Copy link
Contributor

levkk commented Dec 4, 2023

I relaunched the job, let's see if it passes this time. The code looks good to me.

@levkk levkk merged commit 4dbef49 into postgresml:main Dec 5, 2023
1 check passed
levkk added a commit that referenced this pull request Dec 5, 2023
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.

2 participants