Skip to content

Update PR data Daily collection (2025-07-09 01:43 UTC) #117

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.

Sign up for GitHub

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

Merged
gounthar merged 1 commit into from
Jul 9, 2025
+313 −243
Merged

Update PR data Daily collection (2025-07-09 01:43 UTC) #117

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions data/consolidated/all_prs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6624,38 +6624,38 @@
"statusCheckRollup": [
{
"__typename": "CheckRun",
"completedAt": "2025-04-15T15:13:41Z",
"completedAt": "2025-07-08T12:15:36Z",
"conclusion": "SUCCESS",
"detailsUrl": "https://github.com/jenkinsci/git-push-plugin/actions/runs/14472963928/job/40591425929",
"detailsUrl": "https://github.com/jenkinsci/git-push-plugin/actions/runs/16142863164/job/45554195023",
"name": "security-scan / scan",
"startedAt": "2025-04-15T15:11:05Z",
"startedAt": "2025-07-08T12:12:14Z",
"status": "COMPLETED",
"workflowName": "Jenkins Security Scan"
Comment on lines +6627 to 6633
Copy link
Contributor

@coderabbitai coderabbitai bot Jul 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify startedAt ≤ completedAt for every status check
While the sample objects here look fine (e.g., 12:12:14 → 12:15:36), it’s easy for automated refresh jobs to accidentally swap or mis-format timestamps elsewhere in this 6 k-line file. A silent ordering error would break any downstream SLA / duration metrics.

Also applies to: 6644-6650, 6654-6660

🏁 Script executed:

#!/bin/bash
# Fail if any CheckRun or StatusContext has completedAt earlier than startedAt
jq -r '..|objects|select(has("startedAt") and has("completedAt"))| [.startedAt,.completedAt] | @tsv' \
  data/consolidated/all_prs.json |
awk 'BEGIN{err=0}
     { if ($1 > $2) {print "⛔  " $0; err=1} }
     END{ exit err }'

Length of output: 14396

Detected timestamp ordering errors in all_prs.json – fixes required
The automated check found numerous entries where completedAt is earlier than startedAt, which will break SLA/duration metrics downstream. Please correct these timestamp fields at the data source or normalize the JSON so that every status check satisfies startedAt ≤ completedAt.

Affected locations (examples):

  • data/consolidated/all_prs.json (around lines 6627–6633, 6644–6650, 6654–6660, and many more)
    Sample mismatches:
    • 2025-03-27T21:58:21Z → 2025-03-27T21:58:20Z
    • 2025-03-27T21:58:19Z → 2025-03-27T21:58:18Z
    • 2025-03-11T11:36:02Z → 2025-03-11T11:36:01Z
    …and dozens more.

Recommended action:

  1. Update the process that generates or merges these timestamps so that completedAt is never before startedAt.
  2. Re-run the verification script to confirm all entries now satisfy the correct ordering.
🤖 Prompt for AI Agents 
In data/consolidated/all_prs.json around lines 6627 to 6633, there are entries
where the completedAt timestamp is earlier than the startedAt timestamp, causing
ordering errors. To fix this, update the data generation or merging process to
ensure that for every entry, completedAt is always equal to or later than
startedAt. After making these corrections, re-run the verification script to
confirm all timestamp orderings are valid.

},
{
"__typename": "StatusContext",
"context": "continuous-integration/jenkins/pr-head",
"startedAt": "2025-04-15T15:11:42Z",
"startedAt": "2025-07-08T12:15:24Z",
"state": "ERROR",
"targetUrl": "https://ci.jenkins.io/job/Plugins/job/git-push-plugin/job/PR-103/2/display/redirect"
"targetUrl": "https://ci.jenkins.io/job/Plugins/job/git-push-plugin/job/PR-103/3/display/redirect"
},
{
"__typename": "CheckRun",
"completedAt": "2025-04-15T15:11:33Z",
"completedAt": "2025-07-08T12:15:23Z",
"conclusion": "FAILURE",
"detailsUrl": "https://ci.jenkins.io/job/Plugins/job/git-push-plugin/job/PR-103/2/display/redirect",
"detailsUrl": "https://ci.jenkins.io/job/Plugins/job/git-push-plugin/job/PR-103/3/display/redirect",
"name": "Jenkins",
"startedAt": "2025-04-15T15:10:59Z",
"startedAt": "2025-07-08T12:12:22Z",
"status": "COMPLETED",
"workflowName": ""
},
{
"__typename": "CheckRun",
"completedAt": "2025-04-15T15:13:38Z",
"completedAt": "2025-07-08T12:16:31Z",
"conclusion": "SUCCESS",
"detailsUrl": "https://github.com/jenkinsci/git-push-plugin/runs/40591619928",
"detailsUrl": "https://github.com/jenkinsci/git-push-plugin/runs/45554440115",
"name": "Jenkins Security Scan",
"startedAt": "2025-04-15T15:13:29Z",
"startedAt": "2025-07-08T12:15:23Z",
"status": "COMPLETED",
"workflowName": ""
}
Expand Down
22 changes: 11 additions & 11 deletions data/consolidated/open_prs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4697,38 +4697,38 @@
"statusCheckRollup": [
{
"__typename": "CheckRun",
"completedAt": "2025-04-15T15:13:41Z",
"completedAt": "2025-07-08T12:15:36Z",
"conclusion": "SUCCESS",
"detailsUrl": "https://github.com/jenkinsci/git-push-plugin/actions/runs/14472963928/job/40591425929",
"detailsUrl": "https://github.com/jenkinsci/git-push-plugin/actions/runs/16142863164/job/45554195023",
"name": "security-scan / scan",
"startedAt": "2025-04-15T15:11:05Z",
"startedAt": "2025-07-08T12:12:14Z",
"status": "COMPLETED",
"workflowName": "Jenkins Security Scan"
Comment on lines +4700 to 4706
Copy link
Contributor

@coderabbitai coderabbitai bot Jul 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Sanity-check startedAt ≤ completedAt across the roll-up

For the lines shown the ordering looks correct (e.g. 12:12:14Z → 12:15:36Z), but we’ve had a few historical regressions where large data refreshes introduced inverted timestamps on other entries.
Recommend running a quick jq/awk scan before merging:

Expect: no output.
If anything is printed, the JSON slice should be fixed before landing.

Also applies to: 4711-4713, 4717-4724, 4727-4734

🏁 Script executed:

#!/bin/bash
# Fail if any CheckRun has startedAt > completedAt
jq -r '..|objects|select(.startedAt? and .completedAt?)|
        select(.startedAt > .completedAt)|
        "\(.name)  \(.startedAt) > \(.completedAt)"' \
   data/consolidated/open_prs.json

Length of output: 15614

Fix inverted startedAt/completedAt timestamps in open_prs.json

A full jq scan uncovered multiple entries where startedAt is later than completedAt, for example:

  • SpotBugs: 2025-03-11T11:36:02Z > 2025-03-11T11:36:01Z
  • CPD: 2025-03-11T11:36:06Z > 2025-03-11T11:36:05Z
  • CheckStyle: 2025-03-11T11:36:04Z > 2025-03-11T11:36:02Z
  • Code Coverage: 2025-03-11T11:35:46Z > 2025-03-11T11:35:45Z
  • …and many more across the file

These inversions appear in the following sections:

  • Lines 4700–4706
  • Lines 4711–4713
  • Lines 4717–4724
  • Lines 4727–4734

Please correct all affected timestamp pairs before merging. You can rerun this check to verify you’ve fixed them:

jq -r '..|objects|select(.startedAt? and .completedAt?)|
        select(.startedAt > .completedAt)|
        "\(.name)  \(.startedAt) > \(.completedAt)"' \
   data/consolidated/open_prs.json

Expect no output once all entries are corrected.

🤖 Prompt for AI Agents 
In data/consolidated/open_prs.json around lines 4700 to 4706, the startedAt and
completedAt timestamps are inverted, with startedAt being later than
completedAt. Review these entries and swap the values of startedAt and
completedAt wherever startedAt is greater than completedAt to ensure
chronological order. Repeat this correction for all affected sections mentioned,
then rerun the provided jq command to verify no inverted timestamps remain.

},
{
"__typename": "StatusContext",
"context": "continuous-integration/jenkins/pr-head",
"startedAt": "2025-04-15T15:11:42Z",
"startedAt": "2025-07-08T12:15:24Z",
"state": "ERROR",
"targetUrl": "https://ci.jenkins.io/job/Plugins/job/git-push-plugin/job/PR-103/2/display/redirect"
"targetUrl": "https://ci.jenkins.io/job/Plugins/job/git-push-plugin/job/PR-103/3/display/redirect"
},
{
"__typename": "CheckRun",
"completedAt": "2025-04-15T15:11:33Z",
"completedAt": "2025-07-08T12:15:23Z",
"conclusion": "FAILURE",
"detailsUrl": "https://ci.jenkins.io/job/Plugins/job/git-push-plugin/job/PR-103/2/display/redirect",
"detailsUrl": "https://ci.jenkins.io/job/Plugins/job/git-push-plugin/job/PR-103/3/display/redirect",
"name": "Jenkins",
"startedAt": "2025-04-15T15:10:59Z",
"startedAt": "2025-07-08T12:12:22Z",
"status": "COMPLETED",
"workflowName": ""
},
{
"__typename": "CheckRun",
"completedAt": "2025-04-15T15:13:38Z",
"completedAt": "2025-07-08T12:16:31Z",
"conclusion": "SUCCESS",
"detailsUrl": "https://github.com/jenkinsci/git-push-plugin/runs/40591619928",
"detailsUrl": "https://github.com/jenkinsci/git-push-plugin/runs/45554440115",
"name": "Jenkins Security Scan",
"startedAt": "2025-04-15T15:13:29Z",
"startedAt": "2025-07-08T12:15:23Z",
"status": "COMPLETED",
"workflowName": ""
}
Expand Down
Loading