From: Jenkins Builder Robot <jenkins@linuxtv.org>
To: mchehab@kernel.org, linux-media@vger.kernel.org,
libcamera-devel@lists.libcamera.org
Subject: Build failed in Jenkins: libcamera #359
Date: Sun, 15 Nov 2020 22:27:42 +0000 (UTC) [thread overview]
Message-ID: <1795520440.46.1605479262655@builder.linuxtv.org> (raw)
In-Reply-To: <759461501.39.1605258198400@builder.linuxtv.org>
See <https://builder.linuxtv.org/job/libcamera/359/display/redirect>
Changes:
------------------------------------------
Started by an SCM change
Running as SYSTEM
Building on master in workspace <https://builder.linuxtv.org/job/libcamera/ws/>
The recommended git tool is: NONE
No credentials specified
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://linuxtv.org/libcamera.git # timeout=10
Fetching upstream changes from git://linuxtv.org/libcamera.git
> git --version # timeout=10
> git --version # 'git version 2.20.1'
> git fetch --tags --force --progress -- git://linuxtv.org/libcamera.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
FATAL: Invalid id: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information
org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information
at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:203)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:1041)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:331)
at hudson.plugins.git.util.DefaultBuildChooser.getHeadRevision(DefaultBuildChooser.java:129)
at hudson.plugins.git.util.DefaultBuildChooser.getCandidateRevisions(DefaultBuildChooser.java:111)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1145)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1298)
at hudson.scm.SCM.checkout(SCM.java:505)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1206)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1894)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:428)
next prev parent reply other threads:[~2020-11-15 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 10:33 Build failed in Jenkins: libcamera #357 Jenkins Builder Robot
2020-11-13 9:03 ` Build failed in Jenkins: libcamera #358 Jenkins Builder Robot
2020-11-15 22:27 ` Jenkins Builder Robot [this message]
2020-11-15 22:28 ` Build failed in Jenkins: libcamera #360 Jenkins Builder Robot
2020-11-16 5:55 ` Jenkins build is back to normal : libcamera #361 Jenkins Builder Robot
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=1795520440.46.1605479262655@builder.linuxtv.org \
--to=jenkins@linuxtv.org \
--cc=libcamera-devel@lists.libcamera.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/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).