Share via


Setting Schedule Options

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

On the Schedule Options tab you can specify run settings and schedule behavior. You can also select the Result Collection to be associated with the results.

To add options to a schedule

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

  1. When creating a job schedule, select the Schedule Options tab.

  2. Type a name in the Result Collection box or select a file using the Browse button.

  3. From the Start Trying to Schedule this Job drop-down list, select when the Scheduler should start trying to schedule the job. If you choose No Sooner Than, enter a time and date in the Date box as well.

  4. Enter a time limit for the scheduler in the Give up trying to schedule after boxes.

  5. Enter a time-out limit for the job in the Time out boxes.

    Note  Setting the Time Out to 0:0:0 will set the time out period to be infinite.

  6. Select the Schedule Behavior Settings that fit the needs of your test case:

    • Smart Scheduler - The Smart Scheduler will automatically schedule your job, and will use config jobs to modify your test computer to make it fit the job constraints you have set, if necessary.

    • Normal - The normal Scheduler is set to schedule the job, on the timeframe you specified above.

    • Manual - The job result is created in the Manual pipeline. The job may be manually verified by the user and the result edited accordingly, or the Trigger Execution option in Job Monitor can be used to move the job to the Scheduler pipeline, and the job will be scheduled as normal.

    Additional options:

    • Multiplier Count - Selecting this option schedules the job to run more than once with the same constraints applied to all runs. For each result created in the schedule, copies of the result equal to the multiplier count are generated and then scheduled. This count is primarily designed for stress testing.

      Note  If you increment the number of runs beyond the default value of 1, this will simply add more instances of the jobs to the schedule. These additional instances will run on any computer possible within the machine pool, including the same computer.

    • Private run - Allows a job to be run, but results will be marked as Private so reporting is not skewed.

    • Track failures with Resolver - Use Failure Explorer to track failures.

Using Scheduler

 

 

Build date: 9/14/2012