[Bug][Master] Fix taskInstance's start time might be null when dispatch failed#15290
[Bug][Master] Fix taskInstance's start time might be null when dispatch failed#15290jackyyyyyssss wants to merge 2 commits intoapache:devfrom
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## dev #15290 +/- ##
=========================================
Coverage 38.19% 38.19%
Complexity 4673 4673
=========================================
Files 1278 1278
Lines 44481 44481
Branches 4783 4783
=========================================
Hits 16988 16988
Misses 25631 25631
Partials 1862 1862 ☔ View full report in Codecov by Sentry. |
|
Kudos, SonarCloud Quality Gate passed! |
|
Please retry analysis of this Pull-Request directly on SonarCloud. |
fuchanghai
left a comment
There was a problem hiding this comment.
hi @jackyyyyyssss I refute the point I agreed with before, because according to the logic of the previous version, startTime is the time when the task is in the running state, and startTime in the dispatch state should be null because the task has not really started. We should solve it in another way. this problem , WDYT? cc @ruanwenjun
Thank you for your feedback. It is incorrect to have a start and end time according to this method, but not setting a time will result in the loss of front-end statistical tasks |
hi @jackyyyyyssss can we modify the statistical's interface to fix this bug? |
|
Can you tell me which statistics interface it is? I'd be happy to take a look at it when I have free time. |
|









Purpose of the pull request
If there is only one work and the available resources are very low, the heartbeat will result in no available work Dispatcher method reporting an error, and calling addDispatchFailedEvent will result in an empty starttime. In this case, the task is actually a failure. When querying failed tasks in the foreground, the count is incorrect because the starttime is empty


Brief change log
Verify this pull request
This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(or)
If your pull request contain incompatible change, you should also add it to
docs/docs/en/guide/upgrede/incompatible.md