You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[CI] API diff: 'Publish GitHub comment for change detection' fails with git ancestry error #26107
Error:Publish GitHub comment for change detection step fails Pipeline:xamarin-macios-pr-apidiff Category: Infrastructure / Script bug Period: July 8–15, 2026
Problem
The "Publish GitHub comment for change detection" step in the API diff pipeline fails with a git ancestry check error. The script attempts to determine whether the build commit is an ancestor of the target branch, but this check fails, causing the task to exit with code 1.
Since the task has continueOnError: true, builds are marked partiallySucceeded rather than failed, but API diff comments are not posted on the affected PRs.
Error Message
Error checking if current commit is latest in PR: Failed to determine whether '<commit>' is an ancestor of 'origin/<target_branch>'.
The failure occurs across multiple target branches (xcode27.0, main), suggesting the git ancestry check script has a general bug rather than a branch-specific issue. The script runs on Azure Pipelines hosted Windows agents (not macOS bots), and the git fetch may not be retrieving enough history for the ancestry check to work.
This issue was automatically generated by CI post-mortem analysis.
Failed to determine whether 'f3442a10...' is an ancestor of 'origin/net11.0'
Not reopening — the fix in #26144 was merged Jul 22 01:07 UTC (less than 2 weeks ago). PR#26242 was created at 16:18 UTC the same day, so it should have the fix in its target branch. Possible explanations:
The PR branch was created before a git fetch that picked up the fix
The shallow checkout in CI didn't have enough history for the ancestry check
No further occurrences after Jul 22 (4 apidiff builds on Jul 27 all succeeded). Likely resolved.
Activity
[devops] Fix apidiff GitHub comment step failing on git ancestry check …
rolfbjarne commentedon Jul 27, 2026
CI Post-Mortem Update (July 20–27, 2026)
This failure recurred once after the fix was merged:
Failed to determine whether 'f3442a10...' is an ancestor of 'origin/net11.0'Not reopening — the fix in #26144 was merged Jul 22 01:07 UTC (less than 2 weeks ago). PR#26242 was created at 16:18 UTC the same day, so it should have the fix in its target branch. Possible explanations:
git fetchthat picked up the fixNo further occurrences after Jul 22 (4 apidiff builds on Jul 27 all succeeded). Likely resolved.