VSTest task in Azure devops timing out after 60 minutes

Question

I implemented a test method using MSTest2, the execution of the test code takes about a minute. This test uses DataTestMethod with DynamicData source. The result of expansion of the dynamic data results in more than a 100 tests. When I run the test in Azure Pipeline, the test times out exactly at 60 minutes. I've tried several options

Timeout on job
customRunTimePerBatchValue on the test input.

Neither works! It makes using DataTestMethod useless. Any suggestions of how to fix this?

Regards.

Previously I had mentioned job above when I actually meant Task as that's what I had tried. Putting the timeout on the job seems to fix it.

Are you using a hosted agent? https://learn.microsoft.com/en-us/azure/devops/pipelines/process/phases?view=azure-devops&tabs=yaml#timeouts — Daniel Mann, Mar 23 '21 at 21:50

score 3 · Accepted Answer · answered Mar 24 '21 at 01:59

3

Agree with Daniel,

If your project is private and you are using hosted agent, check this doc: One free parallel job that can run for up to 60 minutes each time, until you've used 1,800 minutes (30 hours) per month. You can pay for additional capacity per parallel job. Paid parallel jobs remove the monthly time limit and allow you to run each job for up to 360 minutes (6 hours). Buy Microsoft-hosted parallel jobs.

Another way is configure self-hosted agent and open build definition->click option tab and change the value of field Build job timeout in minutes to 0, then it should be work. We could check this doc for more details.

answered Mar 24 '21 at 01:59

Vito Liu

7,525
1
8
17

Liu - PM'd you offline. – loganwol Mar 24 '21 at 22:33
Hi @loganwol, I am online now. It seems that you have solved the problem and thanks for the sharing – Vito Liu Mar 25 '21 at 01:45
1

Thanks for clue, @Vito. – loganwol Mar 25 '21 at 23:00

score 1 · Answer 2 · answered Mar 25 '21 at 00:47

1

Setting timeoutInMinutes: 0 on the job (not on the VSTest task) seems to remove the 60 minute restriction.

answered Mar 25 '21 at 00:47

loganwol

97
1
9

Hi, Thanks for the sharing, you could [Accept it as an Answer](https://meta.stackexchange.com/questions/5234/how-does-accepting-an-answer-work/5235#5235) , it could help other community members who get the same issues and we could archive this thread. Thanks. Have a nice day. :) – Vito Liu Mar 31 '21 at 06:26

score 1 · Answer 3 · answered Apr 30 '22 at 10:39

For self-hosted agents, in case your pipeline is built using 'yaml' file (a CI pipeline), then you may want to set the VSTest@2 as a task under 'jobs' as shown below:

jobs:
- job: myJob
  timeoutInMinutes: 0
  pool:
    name: myTestAgentPool
  steps:
  - task: VSTest@2
    displayName: 'Test run for Test plans'
    inputs:
      testSelector: testPlan
      testPlan: xxxxx
      testSuite: xxxxx

Setting 'timeoutInMinutes' to 0 will remove any timeout limitation for all steps under 'myJob'. You can setup different jobs likewise.

VSTest task in Azure devops timing out after 60 minutes

3 Answers3