infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Commented] (INFRA-16808) Jenkins GitException "fatal: unable to read tree"
Date Thu, 26 Jul 2018 03:50:00 GMT


Chris Lambertus commented on INFRA-16808:

I only suggest it to rule out a network issue because github has better network peering than
git-wip. The github mirror is created by us and synced by us, so it should still reflect a
source of truth, although with git-wip (i.e. NOT gitbox) repos, it is considered non-canonical.

> Jenkins GitException "fatal: unable to read tree"
> -------------------------------------------------
>                 Key: INFRA-16808
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Patrick Hunt
>            Assignee: Chris Lambertus
>            Priority: Major
> We're seeing some Jenkins jobs fail due to the following:
> Caused by: hudson.plugins.git.GitException: Command "git reset --hard" returned status
code 128:
> stdout: 
> stderr: fatal: unable to read tree 4d579c6c4dd72a231d20e53a2ec357c48c331d20
> This is for
>  > git config remote.origin.url git:// # timeout=10
> and seems to be happening on certain hosts for certain jobs.
> I'm guessing that the git workspace is corrupted? What's the right way to handle something
like this from a project perspective? Should I be specifying an "Additional Behaviours" of
some kind? Any help would be appreciated.
> Here are two hosts I've seen recently:
> H22:
> H32:
> different job,
> H30:

This message was sent by Atlassian JIRA

View raw message