Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Violation of PRIMARY KEY constraint 'PK__BuildTestResults' error when running MSTest action

    Scheduled Pinned Locked Moved Support
    buildmastermstestnetunit-tests
    2 Posts 1 Posters 7 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      We have tests running with MSTest.exe via BuildMaster. As test file we specify dll that contains some unit tests. In the log we get the information that all tests pass and the following error message:

      An unhandled exception occurred while executing this action: System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK__BuildTestResults'. Cannot insert duplicate key in object 'dbo.BuildTestResults'. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Inedo.BuildMaster.Data.StandardDataFactory.ExecuteNonQuery(String storedProcName, DbParameter[] parameters) at Inedo.BuildMaster.Data.DataFactory.Inedo.Data.IDataFactory.ExecuteNonQuery(String storedProcName, DbParameter[] parameters) at Inedo.Data.WrappedStoredProc.ExecuteNonQuery() at Inedo.BuildMaster.Extensibility.Actions.Testing.UnitTestActionBase.Execute() at Inedo.BuildMaster.Extensibility.Actions.ActionBase.ParamlessExecute()

      We also use MSTest action with other dlls in BuildMaster build plan and they execute with no errors.

      Thanks

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        We have a known issue where if you have two test actions with the same group name in the same deployment plan, you will get this error.

        The workaround is to use a different group name for each test action in the same plan.

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation