better to send such info to infra-support to document as a ticket. ( adding infra-support )

On Thu, Dec 1, 2016 at 12:22 PM, Fabian Deutsch <fdeutsch@redhat.com> wrote:
Hey,

so - I have an issue
this job:
is often picking a wrong commit!
http://jenkins.ovirt.org/user/fabiand/my-views/view/ovirt-node-ng/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/219/consoleFull

It says it resetted to master, but master is actually a different commit.
I observed this a few times in the recent days.

Does somebody have an idea why this could be happening?

00:00:02.156 Checking out Revision
c1970c6f7a6404e8ab030147eec81233905345cf (origin/master)

on my local host:
$ git rev-parse FETCH_HEAD^{commit} # timeout=10
9123c1fd3ce15b02f2e69efdc367ae1477193aef

c1970c6f7a6404e8ab030147eec81233905345cf -- does actually no exist (in
my history)

- fabian



--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)