Skip to content
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.

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

[system test]: Optimize execution time in Azure Pipelines #10741

Open
see-quick opened this issue Oct 21, 2024 · 4 comments
Open

[system test]: Optimize execution time in Azure Pipelines #10741

see-quick opened this issue Oct 21, 2024 · 4 comments
Assignees

Comments

@see-quick
Copy link
Member

Related problem

“Currently, in Azure Pipelines, there is a time execution imbalance (e.g., the Regression I. pipeline takes 5 hours and 30 minutes, while the Regression III. pipeline takes only 3 hours and 13 minutes).

Suggested solution

We should make adjustments to optimize all pipelines and avoid these imbalances. See [1].”

[1] - image

Alternatives

No response

Additional context

No response

@im-konge
Copy link
Member

What adjustments would you like to do? I mean, the pipelines are logically split based on the packages and the resources they are testing. Only thing that can be done is to move oauth to security. But it will not fix imbalance with the other pipelines.

@im-konge
Copy link
Member

Also, it can be different for ZK regression:
image

Or you want to solve the imbalance only in the regular regression?

@see-quick
Copy link
Member Author

Well we mainly running regular regressions so for this issue is target to solve that.

the pipelines are logically split based on the packages and the resources

Yeah, but maybe we can find a tests that should be somewhere else or for instance move like you said oauth to security, which would partially fix that problem but that's progress at least.

@im-konge
Copy link
Member

Triaged on 31.10.2024: It makes sense to have a look at it. @see-quick volunteered to have a look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants