FEAT: Add multi-threaded stress tests and stress-test-pipeline #410

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

Draft

gargsaumya wants to merge 1 commit into main from saumya/stress-tests

Draft

FEAT: Add multi-threaded stress tests and stress-test-pipeline #410

Add multi-threaded stress tests and stress-test-pipeline

GitHub Advanced Security / devskim succeeded Jan 21, 2026 in 8s

14 new alerts

New alerts in code changed by this pull request

14 notes

See annotations below for details.

View all branch alerts.

Annotations

Check notice on line 102 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 103 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 104 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 105 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 108 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 120 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 128 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 206 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 207 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 208 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 209 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 212 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 224 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production

Check notice on line 232 in eng/pipelines/stress-test-pipeline.yml

Code scanning / devskim

Accessing localhost could indicate debug code, or could hinder scaling. Note

Do not leave debug code in production