Some weird errors in Jenkins on post-ino64 -CURRENT
Li-Wen Hsu
lwhsu at freebsd.org
Thu Jul 6 12:09:03 UTC 2017
Hi -java,
With FreeBSD cluster update, we migrated several Jenkins builders to
post-ino64 -CURRENT, but since then, we encountered several mysterious
errors.
What happens here is Jenkins (which uses SVNKit, subversion client library
written in Java) refuses checkout codes from svn.freebsd.org. Some logs
like these:
https://ci.freebsd.org/job/FreeBSD-head-amd64-build/3674/console
00:00:10.759 ERROR: Failed to check out svn://svn.freebsd.org/base/head
00:00:10.760 org.tmatesoft.svn.core.SVNException: svn: E200030: BUSY
https://ci.freebsd.org/job/FreeBSD-head-amd64-build/3676/console
00:00:00.104 ERROR: Failed to check out svn://svn.freebsd.org/base/head
00:00:00.104 org.tmatesoft.svn.core.SVNException: svn: E155018:
'/jenkins/workspace/FreeBSD-head-amd64-build/src' already exists and is not
a directory
I've talked this with Ed at BSDCan, and we suspect this is related to
ino64. Normally, recompiling the binaries should solve the problem. But I
have tried to recompile everything that Jenkins depends on but it still
doesn't work. I also tried to use openjdk7 to build a new openjdk7-version
bootstrap-openjdk but it still doesn't help.
This is reproducible with latest -CURRENT snapshot, installing Jenkins and
checking out codes from svn.freebsd.org.
Any ideas, suggest what to test next?
Thanks,
Li-Wen
--
Li-Wen Hsu <lwhsu at FreeBSD.org>
https://lwhsu.org
More information about the freebsd-java
mailing list