That would be cool! I've got a simple test project that drops & creates an nhibernate database, and it's set to run first in the nant scripts. So, in theory, it will cleanup if some previous run has aborted badly (which is what happened a couple of days ago).
Problem I'm having right now is that it isn't talking to the database at all. It certainly has at least once, but doesn't want to now. From what I can tell, the nant scripts update the app.config file with a suitable connection string, but I'm guessing that isn't happening for some reason. On Wed, Mar 17, 2010 at 6:00 PM, Tuna Toksoz <[email protected]> wrote: > I will check the issue simultaneously, if my connection allows me to do a > fresh chekout :) > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksoz > http://tunatoksoz.com > http://twitter.com/tehlike > > > > > > On Wed, Mar 17, 2010 at 6:59 PM, Steve Strong <[email protected]> wrote: > >> If nothing else, this is getting my commit count higher >> >> >> On Wed, Mar 17, 2010 at 5:53 PM, <[email protected]> wrote: >> >>> Build NHibernate::NHibernate Trunk #3.0.0.4961 failed (tests failed: 1, >>> passed: 0) >>> Agent: agent03 >>> Build results: >>> http://teamcity.codebetter.com/viewLog.html?buildId=10821&buildTypeId=bt7 >>> >>> Failed Tests Summary: >>> >>> Failed tests (1 test, alphabetically ordered) >>> ================================================================== >>> NHibernate.TestDatabaseSetup.DatabaseSetup.SetupDatabase >>> >>> >>> >>> Failed tests details (naturally ordered) >>> ================================================================== >>> NHibernate.TestDatabaseSetup.DatabaseSetup.SetupDatabase >>> ================= >>> System.Data.SqlClient.SqlException : A network-related or >>> instance-specific error occurred while establishing a connection to SQL >>> Server. The server was not found or was not accessible. Verify that the >>> instance name is correct and that SQL Server is configured to allow remote >>> connections. (provider: Named Pipes Provider, error: 40 - Could not open a >>> connection to SQL Server)at >>> System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, >>> Boolean breakConnection) >>> at >>> System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject >>> stateObj) >>> at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, >>> SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 >>> timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean >>> integratedSecurity, SqlConnection owningObject) >>> at >>> System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo >>> serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 >>> timerExpire, SqlConnection owningObject) >>> at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String >>> host, String newPassword, Boolean redirectedUserInstance, SqlConnection >>> owningObject, SqlConnectionString connectionOptions, Int64 timerStart) >>> at >>> System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection >>> owningObject, SqlConnectionString connectionOptions, String newPassword, >>> Boolean redirectedUserInstance) >>> at >>> System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity >>> identity, SqlConnectionString connectionOptions, Object providerInfo, String >>> newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) >>> at >>> System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions >>> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection >>> owningConnection) >>> at >>> System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection >>> owningConnection, DbConnectionPool pool, DbConnectionOptions options) >>> at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection >>> owningObject) >>> at >>> System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection >>> owningObject) >>> at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection >>> owningObject) >>> at >>> System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection >>> owningConnection) >>> at >>> System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection >>> outerConnection, DbConnectionFactory connectionFactory) >>> at System.Data.SqlClient.SqlConnection.Open() >>> at NHibernate.TestDatabaseSetup.DatabaseSetup.SetupDatabase() in >>> d:\Builds\NHibernate\nhibernate\src\NHibernate.TestDatabaseSetup\TestDatabaseSetup.cs:line >>> 17 >>> Changes included (1 change) >>> ==================================================== >>> Change 4961 by steverstrong (1 file): >>> Changed app.config to match (hopefully) teamcity setup. Still >>> investigating why the nant scripts didn't update it... >>> >>> see more information about changed files: >>> http://teamcity.codebetter.com/viewLog.html?tab=buildChangesDiv&buildId=10821&buildTypeId=bt7 >>> >>> >>> >>> ============================================================================ >>> Configure email notifications: >>> http://teamcity.codebetter.com/profile.html?init=1#notifications >>> >>> >> >
