petkostas commented on issue #8490:
URL:
https://github.com/apache/incubator-devlake/issues/8490#issuecomment-3183350695
I was able to trace one of the affected runs and found the following:
```json
{
"data": {
"node": {
"__typename": "CheckRun",
"id": "xxxxxxxx",
"name": "xxxxxxxxxxxxx",
"status": "COMPLETED",
"conclusion": "SKIPPED",
"detailsUrl": "https://github.com/lxxxxxxxx";,
"startedAt": "0001-01-01T00:00:00Z",
"completedAt": "2025-07-29T12:10:55Z",
"checkSuite": {
"workflowRun": {
"url": "xxxxx"
}
}
}
}
}
```
It looks like the `startedAt` field is being set to a placeholder value of
**`0001-01-01T00:00:00Z`** for runs that have a **`conclusion`** of
**`SKIPPED`**. I'm trying to confirm this with GitHub, but it seems to be the
case.
This brings up two options for the patch:
1. **Skip the entries** where the run has been skipped.
2. **Assign the `completedAt` value to `startedAt`** for these skipped runs.
Which approach do you think we should take? ( cc: @klesh )
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
