When I click on the “Unit Tests” link to view the test results (see attached screen shot) I get the following error.
An unexpected error occurred: could not execute query [ select unittestas0_.BuildId as BuildId80_, unittestas0_.AssemblyName as Assembly2_80_, unittestas0_.Errors as Errors80_, unittestas0_.NotRun as NotRun80_, unittestas0_.Failed as Failed80_, unittestas0_.Fixed as Fixed80_, unittestas0_.NewFailures as NewFailu7_80_, unittestas0_.Passed as Passed80_, unittestas0_.Shelved as Shelved80_, unittestas0_.Inconclusive as Inconcl10_80_, unittestas0_.TestTime as TestTime80_, unittestas0_.Total as Total80_ from builds_unittestassemblysummary_view unittestas0_ where unittestas0_.BuildId=@p0 order by unittestas0_.TestTime desc, unittestas0_.TestTime desc ] Name:p1 - Value:66278 [SQL: select unittestas0_.BuildId as BuildId80_, unittestas0_.AssemblyName as Assembly2_80_, unittestas0_.Errors as Errors80_, unittestas0_.NotRun as NotRun80_, unittestas0_.Failed as Failed80_, unittestas0_.Fixed as Fixed80_, unittestas0_.NewFailures as NewFailu7_80_, unittestas0_.Passed as Passed80_, unittestas0_.Shelved as Shelved80_, unittestas0_.Inconclusive as Inconcl10_80_, unittestas0_.TestTime as TestTime80_, unittestas0_.Total as Total80_ from builds_unittestassemblysummary_view unittestas0_ where unittestas0_.BuildId=@p0 order by unittestas0_.TestTime desc, unittestas0_.TestTime desc]
This happens across multiple build projects and configurations, for both NUnit and JUnit test result files.
This used to work fine, but some time in the last few weeks it’s stopped working and been giving the above error.
I suspect that your database needs some maintenance. If you are using the bundled PostgreSQL database, you can connect to the database using %Program Files%\VSoft Technologies\ContinuaCI\Server\PostgreSQL\bin\pgAdmin3.exe.
Use the connection details in %Program Files%\VSoft Technologies\ContinuaCI\Server\Continua.Server.Service.exe.config. You can find the connection string under <hibernate-configuration><session-factory><property name=“connection.connection_string”>
Choose a time when the server is not under heavy use, right click on the Continua database and select maintenance. Then select VACUUM and FULL and click OK. Also run a REINDEX using the same maintenance dialog. Let us know if any errors are reported.
Also have a look at the size of the tables in that database. Open the database Schemas node in pgAdmin3.exe and select the Tables node uner the public schema. You can see the table sizes listed on the Statistics tab. The build_unittest table is often large, but if is gets more than say a gigabyte, it would be worth looking into changing your cleanup policy settings.
Another thing to look at is CPU, Memory and Disk usage on the server. If these are high, then the database may have difficultly responding to queries.
We are not using the bundled PostgreSQL database. Instead we are using MS SQL Server. We have just recently upgraded this from 2008 to 2016. I’m thinking this may be the issue. What are your thoughts?
Thank you for the additional information. We have now reproduced the issue. The next version (which we hope to release in the next couple of days) will include a fix.
