G'day,
Not sure if its because I've put the nunit files and results in a different location or a bug in the UI.
Attachment unavailable
And the event log contains…
NHibernate.Exceptions.GenericADOException: could not execute batch command.[SQL: SQL not available] —> System.Data.SqlClient.SqlException: String or binary data would be truncated.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) <br> at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) <br> at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) <br> at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) <br> at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite) <br> at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite) <br> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() <br> at System.Data.SqlClient.SqlCommandSet.ExecuteNonQuery() <br> at NHibernate.AdoNet.SqlClientBatchingBatcher.DoExecuteBatch(IDbCommand ps) <br> --- End of inner exception stack trace --- <br> at NHibernate.AdoNet.SqlClientBatchingBatcher.DoExecuteBatch(IDbCommand ps) <br> at NHibernate.AdoNet.AbstractBatcher.ExecuteBatchWithTiming(IDbCommand ps) <br> at NHibernate.AdoNet.SqlClientBatchingBatcher.AddToBatch(IExpectation expectation) <br> at NHibernate.Persister.Entity.AbstractEntityPersister.Insert(Object id, Object[] fields, Boolean[] notNull, Int32 j, SqlCommandInfo sql, Object obj, ISessionImplementor session) <br> at NHibernate.Persister.Entity.AbstractEntityPersister.Insert(Object id, Object[] fields, Object obj, ISessionImplementor session) <br> at NHibernate.Impl.StatelessSessionImpl.Insert(String entityName, Object entity) <br> at NHibernate.Impl.StatelessSessionImpl.Insert(Object entity) <br> at Continua.Modules.Builds.UnitTests.UnitTestManager.RegisterUnitTests(Int32 buildId, Guid stageId, IList1 unitTests, IEnumerable`1 metrics, Boolean updateMetrics)
Hi Jamie,
Looks like we're hitting a field length limit somewhere. Are you able to send a copy of the unit test xml file to support@finalbuilder.com? It should be listed under the Artifacts tab. This will help us to identify which field is causing the problem.
Emailed the results.
Did the file help resolved the length issue?
Yes, it’s the stack trace field is too long for the database field… we’re looking into it. The field is currently set to nvarchar (max) on sql server, we’re looking at what we can do with this… may have to truncate the data before inserting.
Hmm… don’t think it’s the stacktrace field… still looking into it.
Hi Jamie,
Thanks for sending the results files.
Some of the stack trace fields in your unit test results are over our database field length limit of 10240. We may increase this limit in future, but for now have added some code to truncate these fields to this length.
We hope to get a new build out this afternoon with this fix included.
Note that we have now deleted the results file as per your request.
Hi Jamie,
I've just uploaded a new build (v1.0.0.2280) which contains the fix for this issue.
I’ve just been generating more unit tests with build 2280 and I’ve still got a truncation exception and the view not displaying information. Attached are the details. I suspect the installation program hasn’t installed the changes.
Hi Jamie,
Can you send the latest results.xml file?
We added code to deal with long Stack Trace and Messages fields and the last results.xml file you sent us worked ok, so I'm guessing that we are now over the limit with another field. Unfortunately the exception doesn't tell us which one.
Sent Results.xml to Support At FinalBuilder dot com.
Hi Jamie,
The results.xml file you sent works OK for us so I'm not sure is happening. Does the problem still exist with Build 2324?
Build 2324 (cool build number BTW), correctly displays the unit tests.