infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16808) Jenkins GitException "fatal: unable to read tree"
Date Thu, 26 Jul 2018 04:06:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556867#comment-16556867
] 

Patrick Hunt commented on INFRA-16808:
--------------------------------------

FYI this failure (NoClassDefFoundError: hudson.model.Computer I reported above) is H15:
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-clover/92/console

> Jenkins GitException "fatal: unable to read tree"
> -------------------------------------------------
>
>                 Key: INFRA-16808
>                 URL: https://issues.apache.org/jira/browse/INFRA-16808
>             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://git.apache.org/zookeeper.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: https://builds.apache.org/job/ZooKeeper_branch34_jdk8/1470/console
> H32: https://builds.apache.org/job/ZooKeeper_branch34_jdk8/1469/console
> different job,
> H30: https://builds.apache.org/job/ZooKeeper_branch35_jdk8/1025/console



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message