[Ecm-qa] [QA] FT-nuxeo-master-cmis-dm-tomcat-multiosdb - Build # 52 - Still Failing!

Wed, 16 Jul 2014 05:05:58 -0700

BUILD FAILURE
Build URLhttps://qa.nuxeo.org/jenkins/job/FT-nuxeo-master-cmis-dm-tomcat-multiosdb/52/
Project:FT-nuxeo-master-cmis-dm-tomcat-multiosdb
Date of build:Wed, 16 Jul 2014 08:39:11 +0200
Build duration:5 hr 26 min and counting

CHANGES
  Revision 90c81b68df207d9ade5237d65cd25eb2954132d9 by slacoin:(Revert "NXP-14728 activate managed datasource mode by default in tomcat" (commit: 90c81b68df207d9ade5237d65cd25eb2954132d9))
  editnuxeo-distribution-resources/src/main/resources/templates-tomcat/common-base/nxserver/config/datasources-config.xml.nxftl
  editnuxeo-distribution-resources/src/main/resources/templates-tomcat/common-base/nxserver/config/default-repository-config.xml.nxftl
  editnuxeo-distribution-resources/src/main/resources/templates-tomcat/common-base/nuxeo.defaults

CONSOLE OUTPUT
Started by upstream project "FT-nuxeo-master-cmis-dm-tomcat" build number 109
originally caused by:
Started by upstream project "nuxeo-distribution-master" build number 2604
originally caused by:
Started by GitHub push by nxmatic
Building on master in workspace /jenkins/.jenkins/jobs/FT-nuxeo-master-cmis-dm-tomcat-multiosdb/workspace
> git rev-parse --is-inside-work-tree
Fetching changes from the remote Git repository
> git config remote.origin.url git://github.com/nuxeo/nuxeo-distribution.git
Fetching upstream changes from git://github.com/nuxeo/nuxeo-distribution.git
> git --version
> git fetch --tags --progress git://github.com/nuxeo/nuxeo-distribution.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit}
Checking out Revision 90c81b68df207d9ade5237d65cd25eb2954132d9 (origin/master)
> git config core.sparsecheckout
> git checkout -f 90c81b68df207d9ade5237d65cd25eb2954132d9
> git rev-list b3504dbb4457d1e9ba68cb7bc3864520be3cbc45
No emails were triggered.
Triggering MULTIDB_LINUX,pgsql,openjdk-7-jdk
Configuration MULTIDB_LINUX,pgsql,openjdk-7-jdk is still in the queue: Waiting for next available executor on MULTIDB_LINUX
Triggering MULTIDB_WINDOWS,mysql,openjdk-7-jdk
Triggering MULTIDB_WINDOWS,mssql,openjdk-7-jdk
Triggering MULTIDB_LINUX,oracle11g,openjdk-7-jdk
Triggering MULTIDB_WINDOWS,default,openjdk-7-jdk
Triggering MULTIDB_LINUX,mssql,openjdk-7-jdk
Triggering MULTIDB_LINUX,mysql,openjdk-7-jdk
Triggering MULTIDB_WINDOWS,pgsql,openjdk-7-jdk
Triggering MULTIDB_WINDOWS,oracle11g,openjdk-7-jdk
Configuration MULTIDB_WINDOWS,mysql,openjdk-7-jdk is still in the queue: Waiting for next available executor on MULTIDB_WINDOWS
MULTIDB_WINDOWS,mysql,openjdk-7-jdk completed with result FAILURE
MULTIDB_WINDOWS,mssql,openjdk-7-jdk completed with result FAILURE
MULTIDB_LINUX,oracle11g,openjdk-7-jdk completed with result SUCCESS
MULTIDB_WINDOWS,default,openjdk-7-jdk completed with result SUCCESS
MULTIDB_LINUX,mssql,openjdk-7-jdk completed with result SUCCESS
MULTIDB_LINUX,mysql,openjdk-7-jdk completed with result SUCCESS
MULTIDB_WINDOWS,pgsql,openjdk-7-jdk completed with result FAILURE
MULTIDB_WINDOWS,oracle11g,openjdk-7-jdk completed with result FAILURE
Email was triggered for: Always
Sending email for trigger: Always

_______________________________________________
ECM-QA mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-qa

Reply via email to