Skip to content

[HYP-18237] syncstart yaml hyp #2146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 26, 2025
+19 −22
Merged

[HYP-18237] syncstart yaml hyp #2146

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 18 additions & 22 deletions docs/deep-dive-into-hyperexecute-yaml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1755,25 +1755,21 @@ framework:
- "-Dplatname=win"
```

<!-- GENERAL ENDED-->


<nav aria-label="breadcrumbs">
<ul className="breadcrumbs">
<li className="breadcrumbs__item">
<a className="breadcrumbs__link" target="_self" href="https://www.lambdatest.com">
Home
</a>
</li>
<li className="breadcrumbs__item">
<a className="breadcrumbs__link" target="_self" href="https://www.lambdatest.com/support/docs/">
Support
</a>
</li>
<li className="breadcrumbs__item breadcrumbs__item--active">
<span className="breadcrumbs__link">
Deep Dive into HyperExecute YAML
</span>
</li>
</ul>
</nav>
### `syncStart`
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.

To support this, HyperExecute provides the `syncStart` directive in the job YAML.

```yaml
execution:
syncStart: true
```

- When `syncStart` is enabled, the job ensures that all VMs are allocated and ready before starting scenario execution i.e. tests.
- The system waits for up to 15 minutes for all required VMs to become available.
- If all VMs are allocated within this window → tasks start together.
- If some VMs are still pending after 15 minutes → the job proceeds with the allocated VMs.

> 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

<!-- GENERAL ENDED-->
1 change: 1 addition & 0 deletions docs/hyperexecute-yaml-parameters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,6 +165,7 @@ The **HyperExecute YAML** file serves as the foundational component for test exe
| [project](/support/docs/deep-dive-into-hyperexecute-yaml/#project) | String | Segregate data at a project/repo level |
| [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. |
| [afterEachScenario](/support/docs/deep-dive-into-hyperexecute-yaml/#aftereachscenario) | List of Strings | Allows you to trigger your define tasks after each test scenario. |
| [syncStart](/support/docs/deep-dive-into-hyperexecute-yaml/#execution) | Map | Ensures all VMs are ready before starting parallel tasks. |

<nav aria-label="breadcrumbs">
<ul className="breadcrumbs">
Expand Down
Loading