See <https://builds.apache.org/job/dir-fortress-core-docker-test/245/changes>
Changes: [mail] Rerun tests as described in the readme. Also stop execution if one ------------------------------------------ Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H10 (docker Ubuntu ubuntu yahoo-not-h2) in workspace <https://builds.apache.org/job/dir-fortress-core-docker-test/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git # > timeout=10 Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress > https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git > +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision 41fef2432f1e845130046eecf56efd94d4c66834 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 41fef2432f1e845130046eecf56efd94d4c66834 > git rev-list 6ec68526ca58219ce8ed1eb6d137ec9cb8d6b42b # timeout=10 ERROR: Maven Home /home/jenkins/tools/maven/latest3 doesn?t exist
