List for cgit developers and users
 help / color / mirror / Atom feed
From: noreply at jenkins-public.pelagic.nl (Pelagic Jenkins (Public) )
Subject: Build failed in Jenkins: cgit-master-coverity #48 - origin/master - dbaee26
Date: Fri, 19 Jan 2018 12:23:13 +0100 (CET)	[thread overview]
Message-ID: <1856909917.0.1516360993141.JavaMail.jenkins@jenkins-public.internal.Hupie.com> (raw)

See <https://hupie.dyndns.org:15051/jenkins/job/cgit-master-coverity/48/display/redirect?page=changes>

Changes:

[mail] git: update to v2.15.1

[Jason] git: update to v2.16.0

[Jason] ui-blame: Distinguish hashes column from lines column

[Jason] ui-blame: Break out emit_blame_entry into component methods

[Jason] ui-blame: Make each column into a single table cell

[Jason] ui-blame: Allow syntax highlighting

------------------------------------------
Started by user Ferry Huberts
Building in workspace <https://hupie.dyndns.org:15051/jenkins/job/cgit-master-coverity/ws/>
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url http://git.zx2c4.com/cgit # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
 > git submodule foreach --recursive git reset --hard # timeout=10
 > git submodule foreach --recursive git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://git.zx2c4.com/cgit
 > git --version # timeout=10
 > git fetch --tags --progress http://git.zx2c4.com/cgit +refs/heads/*:refs/remotes/origin/* --prune
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision dbaee2672be14374acb17266477c19294c6155f3 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f dbaee2672be14374acb17266477c19294c6155f3
Commit message: "ui-blame: Allow syntax highlighting"
 > git rev-list --no-walk 67d0f870506e3bc3703ae3cb2cb00e19691ce967 # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
 > git submodule foreach --recursive git reset --hard # timeout=10
 > git submodule foreach --recursive git clean -fdx # timeout=10
 > git remote # timeout=10
 > git submodule init # timeout=10
 > git submodule sync # timeout=10
 > git config --get remote.origin.url # timeout=10
 > git submodule init # timeout=10
 > git config -f .gitmodules --get-regexp ^submodule\.([^ ]+)\.url # timeout=10
 > git config --get submodule.git.url # timeout=10
 > git config -f .gitmodules --get submodule.git.path # timeout=10
 > git submodule update --init --recursive git
Set build name.
New build name is '#48 - origin/master - dbaee26'
[workspace] $ /bin/bash /tmp/jenkins2862263478638179531.sh
Build step 'Execute shell' marked build as failure
Set build name.
New build name is '#48 - origin/master - dbaee26'
Archiving artifacts


                 reply	other threads:[~2018-01-19 11:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1856909917.0.1516360993141.JavaMail.jenkins@jenkins-public.internal.Hupie.com \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).