Skip to content

Instantly share code, notes, and snippets.

@qlijarvis

qlijarvis/pr_only_checker_log_detailed.md

Created November 6, 2026 07:25
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save qlijarvis/0e2bcebb19c237a13987de9f07bb6368 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save qlijarvis/0e2bcebb19c237a13987de9f07bb6368 to your computer and use it in GitHub Desktop.
Download ZIP
PR #2176 checker-log-analyzer detailed analysis
Raw
pr_only_checker_log_detailed.md

PR #2176 — checker-log-analyzer Detailed Analysis

PR: qualcomm-linux/kernel-topics#2176 Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175823636

Report

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #2176 - QCLINUX: arm64: dts: qcom: add Nord CAMX EL2 overlay
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175823636

Checker Result Summary
checkpatch ⏭️ CI infrastructure failure - no jobs ran
dt-binding-check ⏭️ CI infrastructure failure - no jobs ran
dtb-check ⏭️ CI infrastructure failure - no jobs ran
sparse-check ⏭️ CI infrastructure failure - no jobs ran
check-uapi-headers ⏭️ CI infrastructure failure - no jobs ran
check-patch-compliance ⏭️ CI infrastructure failure - no jobs ran
tag-check N/A Cannot determine target branch (network unavailable)
qcom-next-check N/A Cannot determine target branch (network unavailable)

⚠️ CI Infrastructure Failure

Root cause: All checker jobs failed during the merge preparation phase with "fatal: refusing to merge unrelated histories" when attempting to merge PR #2176 with the topic branch topic/tech/overlay/dt.

Failure details:

Merging topic branches...
------------------------------------------
 ** Merging topic branch: topic/tech/overlay/dt
fatal: refusing to merge unrelated histories
Merge failed, manual merge
...
Fetching PR #2176 from https://github.com/qualcomm-linux/kernel-topics.git...
From https://github.com/qualcomm-linux/kernel-topics
 * [new ref]                   refs/pull/2176/head -> pr-2176
Merging pr-2176 (no-commit)...
fatal: refusing to merge unrelated histories
Merge failed or conflicts detected. Aborting merge.
##[error]Process completed with exit code 3.

Analysis:
This is a CI infrastructure/configuration issue, not a patch defect. The error occurs because:

  1. The CI workflow attempts to merge the PR branch with the integration baseline and topic branch topic/tech/overlay/dt
  2. Git refuses to merge because the PR branch and the topic branch have completely unrelated commit histories (no common ancestor)
  3. This typically happens when:
    • The PR was created from an orphan branch or a different repository
    • The topic branch topic/tech/overlay/dt has an incompatible history
    • The CI configuration is attempting to merge branches that should not be merged together

Fix:
This requires investigation and action by the repository maintainers:

  1. Verify the PR branch history:

    git log --oneline --graph pr-2176
git merge-base topic/tech/overlay/dt pr-2176

  2. Check if the PR should target a different base branch or if the topic branch configuration needs adjustment

  3. Possible resolutions:

    • Rebase the PR branch onto the correct base that shares history with topic/tech/overlay/dt
    • Remove topic/tech/overlay/dt from the CI merge configuration if it's not applicable to this PR
    • Use git merge --allow-unrelated-histories in the CI workflow (only if intentional)

Reproduce locally:

# Clone the repo and fetch the PR
git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics
git fetch origin pull/2176/head:pr-2176
git fetch origin topic/tech/overlay/dt

# Attempt the merge that CI is trying
git checkout -b test-merge <baseline-sha>
git merge topic/tech/overlay/dt
git merge pr-2176  # This will fail with "refusing to merge unrelated histories"

📋 Static Patch Analysis (without CI execution)

Since the checkers could not run, I performed a static analysis of the patch content:

Potential checkpatch issues:

  1. LONG_LINE warning - One line exceeds 100 characters:

    Line 130 chars: nord-ride-embedded-camx-el2-dtbs := nord-ride-embedded.dtb nord-embedded-el2.dtbo nord-ride-embedded-camx.dtbo nord-camx-el2.dtbo
    • Severity: WARNING (not ERROR)
    • Fix: This is a Makefile variable assignment. Makefiles often have long lines for build rules. This may be acceptable, but could be wrapped with backslash continuation if needed.

  2. Subject prefix: QCLINUX:

    • The commit uses QCLINUX: prefix, which indicates a vendor-only change
    • This prefix will always fail check-patch-compliance because it's not in the allowed upstream prefix list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:)
    • This is a known limitation of the checker for vendor-only commits
    • No action needed if this is intentionally a vendor-only change with no upstream equivalent

Patch content looks clean:

  • ✅ Has Signed-off-by: trailer
  • ✅ No trailing whitespace
  • ✅ Proper SPDX license identifier
  • ✅ DTS overlay syntax appears correct
  • ✅ Makefile syntax appears correct

Verdict

CI must be fixed before any checker results are available.

The PR cannot be evaluated by the kernel-checkers CI until the "unrelated histories" merge issue is resolved. This is a CI infrastructure problem, not a patch quality issue.

Recommended actions:

  1. Immediate: Repository maintainers should investigate why the PR branch has unrelated history with topic/tech/overlay/dt
  2. After CI fix: Re-trigger the checker workflow to get actual validation results
  3. Optional: Consider wrapping the 130-character Makefile line if checkpatch complains when CI runs

Note: The QCLINUX: prefix will cause check-patch-compliance to fail when CI runs, but this is expected for vendor-only changes and is not a blocker if the change is intentionally vendor-specific.

Raw agent output

This line is exactly 100 characters. Now let me produce the final analysis report following the skill workflow:

[CHECKER_LOG_REPORT]

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #2176 - QCLINUX: arm64: dts: qcom: add Nord CAMX EL2 overlay
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175823636

Checker Result Summary
checkpatch ⏭️ CI infrastructure failure - no jobs ran
dt-binding-check ⏭️ CI infrastructure failure - no jobs ran
dtb-check ⏭️ CI infrastructure failure - no jobs ran
sparse-check ⏭️ CI infrastructure failure - no jobs ran
check-uapi-headers ⏭️ CI infrastructure failure - no jobs ran
check-patch-compliance ⏭️ CI infrastructure failure - no jobs ran
tag-check N/A Cannot determine target branch (network unavailable)
qcom-next-check N/A Cannot determine target branch (network unavailable)

⚠️ CI Infrastructure Failure

Root cause: All checker jobs failed during the merge preparation phase with "fatal: refusing to merge unrelated histories" when attempting to merge PR #2176 with the topic branch topic/tech/overlay/dt.

Failure details:

Merging topic branches...
------------------------------------------
 ** Merging topic branch: topic/tech/overlay/dt
fatal: refusing to merge unrelated histories
Merge failed, manual merge
...
Fetching PR #2176 from https://github.com/qualcomm-linux/kernel-topics.git...
From https://github.com/qualcomm-linux/kernel-topics
 * [new ref]                   refs/pull/2176/head -> pr-2176
Merging pr-2176 (no-commit)...
fatal: refusing to merge unrelated histories
Merge failed or conflicts detected. Aborting merge.
##[error]Process completed with exit code 3.

Analysis:
This is a CI infrastructure/configuration issue, not a patch defect. The error occurs because:

  1. The CI workflow attempts to merge the PR branch with the integration baseline and topic branch topic/tech/overlay/dt
  2. Git refuses to merge because the PR branch and the topic branch have completely unrelated commit histories (no common ancestor)
  3. This typically happens when:
    • The PR was created from an orphan branch or a different repository
    • The topic branch topic/tech/overlay/dt has an incompatible history
    • The CI configuration is attempting to merge branches that should not be merged together

Fix:
This requires investigation and action by the repository maintainers:

  1. Verify the PR branch history:

    git log --oneline --graph pr-2176
git merge-base topic/tech/overlay/dt pr-2176

  2. Check if the PR should target a different base branch or if the topic branch configuration needs adjustment

  3. Possible resolutions:

    • Rebase the PR branch onto the correct base that shares history with topic/tech/overlay/dt
    • Remove topic/tech/overlay/dt from the CI merge configuration if it's not applicable to this PR
    • Use git merge --allow-unrelated-histories in the CI workflow (only if intentional)

Reproduce locally:

# Clone the repo and fetch the PR
git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics
git fetch origin pull/2176/head:pr-2176
git fetch origin topic/tech/overlay/dt

# Attempt the merge that CI is trying
git checkout -b test-merge <baseline-sha>
git merge topic/tech/overlay/dt
git merge pr-2176  # This will fail with "refusing to merge unrelated histories"

📋 Static Patch Analysis (without CI execution)

Since the checkers could not run, I performed a static analysis of the patch content:

Potential checkpatch issues:

  1. LONG_LINE warning - One line exceeds 100 characters:

    Line 130 chars: nord-ride-embedded-camx-el2-dtbs := nord-ride-embedded.dtb nord-embedded-el2.dtbo nord-ride-embedded-camx.dtbo nord-camx-el2.dtbo
    • Severity: WARNING (not ERROR)
    • Fix: This is a Makefile variable assignment. Makefiles often have long lines for build rules. This may be acceptable, but could be wrapped with backslash continuation if needed.

  2. Subject prefix: QCLINUX:

    • The commit uses QCLINUX: prefix, which indicates a vendor-only change
    • This prefix will always fail check-patch-compliance because it's not in the allowed upstream prefix list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:)
    • This is a known limitation of the checker for vendor-only commits
    • No action needed if this is intentionally a vendor-only change with no upstream equivalent

Patch content looks clean:

  • ✅ Has Signed-off-by: trailer
  • ✅ No trailing whitespace
  • ✅ Proper SPDX license identifier
  • ✅ DTS overlay syntax appears correct
  • ✅ Makefile syntax appears correct

Verdict

CI must be fixed before any checker results are available.

The PR cannot be evaluated by the kernel-checkers CI until the "unrelated histories" merge issue is resolved. This is a CI infrastructure problem, not a patch quality issue.

Recommended actions:

  1. Immediate: Repository maintainers should investigate why the PR branch has unrelated history with topic/tech/overlay/dt
  2. After CI fix: Re-trigger the checker workflow to get actual validation results
  3. Optional: Consider wrapping the 130-character Makefile line if checkpatch complains when CI runs

Note: The QCLINUX: prefix will cause check-patch-compliance to fail when CI runs, but this is expected for vendor-only changes and is not a blocker if the change is intentionally vendor-specific.

[/CHECKER_LOG_REPORT]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment