Ask a questionAsk a question
 

General DiscussionTest Run gets aborted automatically.

  • Saturday, May 02, 2009 11:30 AMRahulJadhav Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    I'm having nearly 60 ordered tests for execution and each of the ordered test is having nearly 15 unit tests in it. It is observed frequently that the Test Run gets aborted suddenly gives a message that is the cause for abortion.
    This seen on many machines.

    Some of the failure message that could b trapped are:
    1. Test run is aborting on 'HYDHTC130851D', number of hung tests exceeds maximum allowable '5'.
    2. Test run exceeded the specified timeout of 2100 seconds.

    Any one if knows the possible causes for this scenario plz share.

    Regards,
    Rahul

All Replies

  • Wednesday, November 04, 2009 9:16 PMJason Horn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello, Rahul,

    I ran into this as well (probably have this resolved by now, but just in case).  The root cause of this, in my case, was that I nested the orderedtest calls too deep.  Meaning that this was self-inflicted damage.

    Here was my scenario (to see if it matches yours).

    parent = orderedtest1
    child = orderedtest2
    grandchild = orderedtest3
    great grandchild = orderedtest4
    great, great grandchild = orderedtest5

    So, I think we both ran into a limitation of VSTS, but hopefully you can reconfigure the tests to workaround this.  I am currently not aware of any exposed setting to override this "feature".

    HTH,

    jason