Skip to content

Conversation

@octo-sts
Copy link
Contributor

@octo-sts octo-sts bot commented Apr 18, 2025

No description provided.

@octo-sts
Copy link
Contributor Author

octo-sts bot commented Apr 18, 2025

🔄 Build Failed: Git Checkout Error

Expected commit ef334dcc399bbda2930ef1f83197718e25053392 for v17.11.0, found 0f67ff190a5f069ef1e46f2a8950e1319e71d6e4

Build Details

Category Details
Build System git
Failure Point git checkout --quiet origin/tags/v17.11.0

Root Cause Analysis 🔍

The git tag v17.11.0 points to a non-commit object (likely a tag object) with hash a5eaa3ae71adcabe6deb185d6f7fc117f333d876, and the commit it references (0f67ff190a5f069ef1e46f2a8950e1319e71d6e4) does not match the expected commit hash (ef334dcc399bbda2930ef1f83197718e25053392) specified in the build configuration.


Was this comment helpful? Please use 👍 or 👎 reactions on this comment.

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Apr 18, 2025
@AmberArcadia AmberArcadia self-assigned this Apr 18, 2025
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Apr 18, 2025
@IdlePhysicist IdlePhysicist self-assigned this Apr 18, 2025
@IdlePhysicist IdlePhysicist requested a review from a team April 18, 2025 23:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai/skip-comment Stop AI from commenting on PR automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. service:version-stream

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants