Skip to content

Update PR test template to allow longer lock testbed time and execution time#22178

Merged
StormLiangMS merged 1 commit intosonic-net:masterfrom
xwjiang-ms:update_pr_test_templates
Feb 2, 2026
Merged

Update PR test template to allow longer lock testbed time and execution time#22178
StormLiangMS merged 1 commit intosonic-net:masterfrom
xwjiang-ms:update_pr_test_templates

Conversation

@xwjiang-ms
Copy link
Contributor

Description of PR

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Approach

What is the motivation for this PR?

Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?

  1. In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
  2. In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

Signed-off-by: xiaweijiang <[email protected]>
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@xwjiang-ms xwjiang-ms changed the title Update PR test template Update PR test template to allow longer lock testbed time and execution time Feb 2, 2026
@StormLiangMS StormLiangMS merged commit 9cecf67 into sonic-net:master Feb 2, 2026
22 checks passed
abhishek-nexthop pushed a commit to nexthop-ai/sonic-mgmt that referenced this pull request Feb 6, 2026
…on time (sonic-net#22178)

What is the motivation for this PR?
Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?
In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.
Signed-off-by: xiaweijiang <[email protected]>
Anirudh-nokia pushed a commit to Anirudh-nokia/sonic-mgmt-fork that referenced this pull request Feb 6, 2026
…on time (sonic-net#22178)

What is the motivation for this PR?
Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?
In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.
Signed-off-by: xiaweijiang <[email protected]>
Signed-off-by: ayya <[email protected]>
nnelluri-cisco pushed a commit to nnelluri-cisco/sonic-mgmt that referenced this pull request Feb 12, 2026
…on time (sonic-net#22178)

What is the motivation for this PR?
Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?
In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.
Signed-off-by: xiaweijiang <[email protected]>
Signed-off-by: nnelluri-cisco <[email protected]>
rraghav-cisco pushed a commit to rraghav-cisco/sonic-mgmt that referenced this pull request Feb 13, 2026
…on time (sonic-net#22178)

What is the motivation for this PR?
Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?
In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.
Signed-off-by: xiaweijiang <[email protected]>
Signed-off-by: Raghavendran Ramanathan <[email protected]>
anilal-amd pushed a commit to anilal-amd/anilal-forked-sonic-mgmt that referenced this pull request Feb 19, 2026
…on time (sonic-net#22178)

What is the motivation for this PR?
Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?
In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.
Signed-off-by: xiaweijiang <[email protected]>
Signed-off-by: Zhuohui Tan <[email protected]>
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
…utomatically (sonic-net#22178)

#### Why I did it
src/sonic-host-services
```
* bccad08 - (HEAD -> 202411, origin/202411) Pin PyGObject to 3.42.2 (sonic-net#307) (3 days ago) [Liu Shilong]
* 1d59da1 - make multi_asic_ns_to_host_fwd False for EXTERNAL_CLIENT ACL service (sonic-net#302) (3 weeks ago) [mssonicbld]
* 5ca4d5d - [202411] cast of kdump init fix (4 weeks ago) [arista-nwolfe]
* ec3a269 - Fix ProcessStatsST column name issue and add test case to cover check (sonic-net#281) (8 weeks ago) [mssonicbld]
* d231ed2 - [202411] Fix 202411 pipeline (sonic-net#290) (8 weeks ago) [Zain Budhwani]
* 1044ca2 - Pin PyGObject to 3.50.0 (sonic-net#233) (5 months ago) [mssonicbld]
```
#### How I did it
#### How to verify it
#### Description for the changelog
ravaliyel pushed a commit to ravaliyel/sonic-mgmt that referenced this pull request Mar 12, 2026
…on time (sonic-net#22178)

What is the motivation for this PR?
Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?
In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.
Signed-off-by: xiaweijiang <[email protected]>
Signed-off-by: Ravali Yeluri (WIPRO LIMITED) <[email protected]>
abhishek-nexthop pushed a commit to nexthop-ai/sonic-mgmt that referenced this pull request Mar 17, 2026
…on time (sonic-net#22178)

What is the motivation for this PR?
Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?
In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.
Signed-off-by: xiaweijiang <[email protected]>
Signed-off-by: Abhishek <[email protected]>
venu-nexthop pushed a commit to venu-nexthop/sonic-mgmt that referenced this pull request Mar 19, 2026
…on time (sonic-net#22178)

What is the motivation for this PR?
Currently we are facing some timeout issue in PR testing, need to update PR test template to fix timeout issues.

How did you do it?
In pipeline level, increase TIMEOUT_IN_MINUTES_PR_TEST to 8 hours in case some azure build-in steps may take a long time.
In elastictest level, increase MAX_RUN_TEST_MINUTES to 6 hours since lock testbed would take longer than before, we need to make sure elastictest has enough time to run test cases.
Signed-off-by: xiaweijiang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants