Skip to content

Commit 1cc2271

Browse files
Merge pull request #2146 from amanchopra1905/stage
[HYP-18237] syncstart yaml hyp
2 parents dc6346b + d7c798f commit 1cc2271

File tree

2 files changed

+19
-22
lines changed

2 files changed

+19
-22
lines changed

docs/deep-dive-into-hyperexecute-yaml.md

Lines changed: 18 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1755,25 +1755,21 @@ framework:
17551755
- "-Dplatname=win"
17561756
```
17571757

1758-
<!-- GENERAL ENDED-->
1759-
1760-
1761-
<nav aria-label="breadcrumbs">
1762-
<ul className="breadcrumbs">
1763-
<li className="breadcrumbs__item">
1764-
<a className="breadcrumbs__link" target="_self" href="https://www.lambdatest.com">
1765-
Home
1766-
</a>
1767-
</li>
1768-
<li className="breadcrumbs__item">
1769-
<a className="breadcrumbs__link" target="_self" href="https://www.lambdatest.com/support/docs/">
1770-
Support
1771-
</a>
1772-
</li>
1773-
<li className="breadcrumbs__item breadcrumbs__item--active">
1774-
<span className="breadcrumbs__link">
1775-
Deep Dive into HyperExecute YAML
1776-
</span>
1777-
</li>
1778-
</ul>
1779-
</nav>
1758+
### `syncStart`
1759+
By default, parallel tasks in autosplit or matrix mode begin execution as soon as the VM is allocated. However, in certain situations (e.g., benchmarking or comparative analysis), you may want all VMs to start tasks at the same time.
1760+
1761+
To support this, HyperExecute provides the `syncStart` directive in the job YAML.
1762+
1763+
```yaml
1764+
execution:
1765+
syncStart: true
1766+
```
1767+
1768+
- When `syncStart` is enabled, the job ensures that all VMs are allocated and ready before starting scenario execution i.e. tests.
1769+
- The system waits for up to 15 minutes for all required VMs to become available.
1770+
- If all VMs are allocated within this window → tasks start together.
1771+
- If some VMs are still pending after 15 minutes → the job proceeds with the allocated VMs.
1772+
1773+
> This feature is supported only in [`autosplit`](/support/docs/deep-dive-into-hyperexecute-yaml/#autosplit) and [`matrix`](/support/docs/deep-dive-into-hyperexecute-yaml/#matrix) mode and not in hybrid mode
1774+
1775+
<!-- GENERAL ENDED-->

docs/hyperexecute-yaml-parameters.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -165,6 +165,7 @@ The **HyperExecute YAML** file serves as the foundational component for test exe
165165
| [project](/support/docs/deep-dive-into-hyperexecute-yaml/#project) | String | Segregate data at a project/repo level |
166166
| [slackChannel](/support/docs/deep-dive-into-hyperexecute-yaml/#slackchannel) | String | Allows you to receive notifications of your Job updates directly in your preferred Slack channel. |
167167
| [afterEachScenario](/support/docs/deep-dive-into-hyperexecute-yaml/#aftereachscenario) | List of Strings | Allows you to trigger your define tasks after each test scenario. |
168+
| [syncStart](/support/docs/deep-dive-into-hyperexecute-yaml/#execution) | Map | Ensures all VMs are ready before starting parallel tasks. |
168169

169170
<nav aria-label="breadcrumbs">
170171
<ul className="breadcrumbs">

0 commit comments

Comments
 (0)