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

doc: update README to test PR squashing #40

Closed
wants to merge 13 commits into from

Conversation

aduh95-test-account
Copy link
Contributor

This is a test.

PR-URL: nodejs/node#39128
Reviewed-By: Mary Marchini <oss@mmarchini.me>
Most PRs are meant to be squashed in one commit when landing. If the
collaborator hasn't been using `fixup!` commits, the CQ lands the PR
as several commits. This change makes the CQ abort by default
when attempting to land several commits, unless there's another
label added to the PR to force squashing or landing as several commits.

Fixes: nodejs/node#40436
Refs: nodejs/node-core-utils#572

PR-URL: nodejs/node#40577
@github-actions
Copy link
Contributor

Commit Queue failed
- Loading data for nodejs/node-auto-test/pull/40
✔  Done loading data for nodejs/node-auto-test/pull/40
----------------------------------- PR info ------------------------------------
Title      doc: update README to test PR squashing (#40)
   ⚠  Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch     aduh95-test-account:test-pr-squashing -> nodejs:main
Labels     fast-track
Commits    1
 - doc: update README to test PR squashing
Committers 1
 - Antoine du Hamel 
PR-URL: https://github.com/nodejs/node-auto-test/pull/40
Reviewed-By: Antoine du Hamel 
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node-auto-test/pull/40
Reviewed-By: Antoine du Hamel 
--------------------------------------------------------------------------------
   ℹ  This PR was created on Sun, 31 Oct 2021 10:02:34 GMT
   ✔  Approvals: 1
   ✔  - Antoine du Hamel (@aduh95) (TSC): https://github.com/nodejs/node-auto-test/pull/40#pullrequestreview-793688411
   ℹ  This PR is being fast-tracked
   ✖  This PR needs to wait 167 more hours to land (or 47 hours if there is one more approval)
   ✖  GitHub CI is still running
   ℹ  Green GitHub Actions CI is sufficient
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node-auto-test/node-auto-test/.ncu
https://github.com/nodejs/node-auto-test/actions/runs/1404418999

@aduh95
Copy link
Contributor

aduh95 commented Oct 31, 2021

@targos can you approve this PR so it can be fast-tracked please?

@github-actions
Copy link
Contributor

Commit Queue failed
- Loading data for nodejs/node-auto-test/pull/40
✔  Done loading data for nodejs/node-auto-test/pull/40
----------------------------------- PR info ------------------------------------
Title      doc: update README to test PR squashing (#40)
   ⚠  Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch     aduh95-test-account:test-pr-squashing -> nodejs:main
Labels     fast-track
Commits    1
 - doc: update README to test PR squashing
Committers 1
 - Antoine du Hamel 
PR-URL: https://github.com/nodejs/node-auto-test/pull/40
Reviewed-By: Antoine du Hamel 
Reviewed-By: Michaël Zasso 
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node-auto-test/pull/40
Reviewed-By: Antoine du Hamel 
Reviewed-By: Michaël Zasso 
--------------------------------------------------------------------------------
   ℹ  This PR was created on Sun, 31 Oct 2021 10:02:34 GMT
   ✔  Approvals: 2
   ✔  - Antoine du Hamel (@aduh95) (TSC): https://github.com/nodejs/node-auto-test/pull/40#pullrequestreview-793688411
   ✔  - Michaël Zasso (@targos) (TSC): https://github.com/nodejs/node-auto-test/pull/40#pullrequestreview-793691367
   ℹ  This PR is being fast-tracked
   ✖  GitHub CI is still running
   ℹ  Green GitHub Actions CI is sufficient
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node-auto-test/node-auto-test/.ncu
https://github.com/nodejs/node-auto-test/actions/runs/1404487166

@targos
Copy link
Member

targos commented Oct 31, 2021

✖ GitHub CI is still running

Maybe we should try to contact GitHub's support about this. It happens sometimes that the API reports pending checks that don't seem to exist.

@aduh95
Copy link
Contributor

aduh95 commented Oct 31, 2021

✖ GitHub CI is still running

Maybe we should try to contact GitHub's support about this. It happens sometimes that the API reports pending checks that don't seem to exist.

Maybe we could also update ncu to ignore those ghost checks. Here's the result of gh api graphql -F prid=40 -F owner=nodejs -F repo=node-auto-test -f query="$(cat …/node-core-utils/lib/queries/PRCommits.gql)":

{
  "data": {
    "repository": {
      "pullRequest": {
        "commits": {
          "nodes": [
            {
              "commit": {
                "checkSuites": {
                  "nodes": [
                    {
                      "id": "CS_kwDOBnE3X877E5v3",
                      "url": "https://github.com/nodejs/node-auto-test/commit/f5b0a228f2265278d1a79bfe4c2affda1d6c2506/checks?check_suite_id=4212366327",
                      "conclusion": null,
                      "status": "QUEUED"
                    },
                    {
                      "id": "CS_kwDOBnE3X877E6TL",
                      "url": "https://github.com/nodejs/node-auto-test/commit/f5b0a228f2265278d1a79bfe4c2affda1d6c2506/checks?check_suite_id=4212368587",
                      "conclusion": "SUCCESS",
                      "status": "COMPLETED"
                    }
                  ]
                },
                "status": null
              }
            }
          ]
        }
      }
    }
  }
}

@targos
Copy link
Member

targos commented Oct 31, 2021

How do we know it's a ghost check?

@aduh95
Copy link
Contributor

aduh95 commented Oct 31, 2021

How do we know it's a ghost check?

Not sure, but if the conclusion is null that seems like a good reason:

The final conclusion of the check. Can be one of action_required, cancelled, failure, neutral, success, skipped, stale, or timed_out.

Also, we could see if there is another check with the same id that has completed for the same commit. EDIT: nope it has different id, that wouldn't work.

@targos
Copy link
Member

targos commented Oct 31, 2021

Not sure, but if the conclusion is null that seems like a good reason

I think it's null because the check is still QUEUED, which is probably also the case for legit checks (like macOS runs that are waiting for a runner in the pool).

@targos
Copy link
Member

targos commented Oct 31, 2021

I created a support ticket.

@panva panva force-pushed the main branch 29 times, most recently from 6fb17d1 to c8e2f3f Compare February 7, 2023 09:21
@panva panva closed this Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants