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.

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

Jump to bottom

remote: fatal: bad object breaking rebase/fanned jobs #3547

Closed
richardlau opened this issue Oct 30, 2023 · 1 comment
Closed

remote: fatal: bad object breaking rebase/fanned jobs #3547

richardlau opened this issue Oct 30, 2023 · 1 comment
Labels
incident

Comments

@richardlau
Copy link
Member

Refs: nodejs/node#48740 (comment)

e.g. https://ci.nodejs.org/job/git-rebase/103263/console

04:23:54 remote: fatal: bad object refs/heads/jenkins-node-test-commit-windows-fanned-7c8137bee077c13a8e4bba42e88a511b2664ddd8-bin-win-vs2022-x86
04:23:54 fatal: bad object refs/heads/jenkins-node-test-commit-windows-fanned-7c8137bee077c13a8e4bba42e88a511b2664ddd8-bin-win-vs2022-x86

I don't think that's due to this PR -- 7c8137b is from #50460. Somehow the temporary binary git repository used in our fanned jobs (Windows and armv7l) has a corrupted reference that build will need to fix.
@richardlau
Copy link
Member Author

Maybe this has fixed itself?
https://ci.nodejs.org/job/git-rebase/ shows a run of broken builds but has been green since 4:38am this morning:

image

@richardlau richardlau mentioned this issue Oct 30, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
incident
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@richardlau