Scheduled Tests Not Executing

6 posts, 0 answers
  1. Some
    Some avatar
    19 posts
    Member since:
    Mar 2009

    Posted 29 Nov 2011 Link to this post

    Hello,
    I am having problems with tests that are scheduled not executing.  The tests run fine when executed from test studio however when I schedule them they do not run.  Originally the scheduling server log was giving me an error saying the execution server was busy even though this was not the case.  After the standard restart services/reboot etc.. with no luck we installed the latest version of Test Studio.  Scheduled tests are still not running with a mixture of messages in the scheduling server log some continuing to say the machine is busy executing other tests and others saying that the project was deployed to a folder and I believe building but nothing further.  Any help or suggestions are appreciated I love this product until this problem came up.

    Thanks
  2. Some
    Some avatar
    19 posts
    Member since:
    Mar 2009

    Posted 01 Dec 2011 Link to this post

    Posting this in case anyone else is having the same problem.  I will determine definitively tomorrow but at the moment things are working again and I believe the issue was I had the same test list scheduled to run at the exact same time twice.  No scheduled runs were appearing on the calendar which had me confused but at the time I noticed it seemed to be the least of my problems.  The messages from the scheduling server logs I mention in my original post were from an ad hoc scheduled run (odd time of day a few minutes in the future from the time at which I was scheduling it).  It wasnt until just a short time ago that I noticed in the logs that it was attempting to run the scheduled test lists whose scheduled runs were not appearing on the calendar.  When it attempted to run them the scheduling server advised it found 2 test runs and when it passed them to the execution server the message in the scheduling log said it was busy running other tests.  I believe it was actually not busy running other tests but rather returned that message on being asked to run the same test list twice.  I believe this then essentially disabled or otherwise broke the execution server so it wouldnt run any more scheduled tests.  
    The fix was to unschedule the two reoccurring schedules for the same test list at the exact same time and reboot the server.  Since those reoccurring schedules didnt appear on the calendar I just deleted the test list and recreated it with a slightly different name.  So far so good will report back if this continues to work going forward.
    Telerik if this does turn out to be the real fix seems like you need to prevent the same test list from being scheduled twice at the same time and also need to fix whatever issue in the calendar is resulting in some of the scheduled runs from not displaying.  Also adjusting the execution server to handle this more gracefully seems like a good idea.  But again will followup and confirm that this in fact does fix the problem permanently and that it doesnt reappear later.
  3. Some
    Some avatar
    19 posts
    Member since:
    Mar 2009

    Posted 01 Dec 2011 Link to this post

    Ok things worked for a while and then they jammed again.  Now I am getting the message "A test list is waiting to be executed on the execution machine......... etc." when attempting to refresh the calendar on the results tab.  This gets back to the problem I was describing before.  The execution server is essentially becoming stuck on a testlist how can I complete or end that testlist manually to let subsequent tests through?
  4. Plamen
    Admin
    Plamen avatar
    8 posts

    Posted 05 Dec 2011 Link to this post

    Hi Some,

    I agree with you, we need to prevent the same test list from being scheduled twice at the same time. I've logged this as a feature request, you can track its progress here: Public URL .

    As for the second issue(from your last post), this strange behavior can be caused by a corrupted SQL database. Please try the following: 

    1.    Close the Execution client.
    2.    Open the "Configure Scheduling Server" menu (see screenshots). 
    3.    Create a new SQL database. To do this simply enter a new name for this database. The rest of the settings can remain the same.
    4.    Now try using scheduling again - the problem should be resolved.

    If this doesn't help, please check out this article and send us the Scheduling log. It's located here by default:
    C:\Program Files (x86)\Telerik\Test Studio 2011.2\Bin\Telerik.TestStudio.Scheduling.Log.

    Hope to hear from you soon!
     
    Best wishes,
    Plamen
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  5. Some
    Some avatar
    19 posts
    Member since:
    Mar 2009

    Posted 06 Dec 2011 Link to this post

    Plamen,
    I appreciate your response.  I setup a new execution server using a new scheduling database I created with the same results.  We have opened a support request however I will share with the community via this forum what the ultimate fix.  So far though the response we received suggests that this could be a bug.

    Thanks
  6. Plamen
    Admin
    Plamen avatar
    8 posts

    Posted 07 Dec 2011 Link to this post

    Hello Some,

    Please send us the Scheduling log, so we can look further into this. If it contains a lot of entries you can clear it, re-run the TestList and trigger the issue again. Then export the log to Excel or Text file and send it to us in a zip file.

    If we are not able to find the root cause of the problem examining the log, we can schedule a GoToMeeting to look at this problem on your machine.

    Hope to hear from you soon!

    Greetings,
    Plamen
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top