-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[Fix][Zeta] Handle null startTimestamp in BaseService
to fix flaky MysqlCDCWithBinlogDeleteIT
test
#9815
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
base: dev
Are you sure you want to change the base?
Conversation
…o fix flaky MysqlCDCWithBinlogDeleteIT test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little curious why it would be null. But this fix also good.
Hi @dybyte . I think add a unit test would be better. But also not a big deal if not. |
I think the NPE occurs because Lines 179 to 196 in 2653f67
|
Should not be. Because the error exception came from rest api. |
I have confirmed that the issue occurs because the job's Lines 305 to 310 in c43d57d
Lines 227 to 233 in c43d57d
This is all I was able to confirm. If you have any additional insights, I would greatly appreciate it. Thank you! |
Oh. Looks make sense. So I think the patch is great! |
Purpose of this pull request
I observed that the
testRestoreTaskWhenBinlogDelete
test inMysqlCDCWithBinlogDeleteIT
occasionally fails in CI.This failure is caused by a NullPointerException in the
getJobStartTime
method ofBaseService
.This PR fixes the NPE in
getJobStartTime
, which eliminates the flakiness of thetestRestoreTaskWhenBinlogDelete
test.Does this PR introduce any user-facing change?
No
How was this patch tested?
Covered by existing test
Check list
New License Guide