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

Run stress tests on private Asp.Net Core package #33860

Merged

Conversation

alnikola
Copy link
Contributor

Currently, it's possible to run stress tests on privately built CoreCLR and libraries by executing load-corefx-testhost.ps1 -b followed by run-docker-compose.ps1 -b. However, it was not possible to run the stress server on a private Asp.Net Core package which is used for private libraries build.

This PR adds a new -pa parameter to run-docker-compose.ps1 which builds a server container with a private Asp.Net Core package version.

@wfurt
Copy link
Member

wfurt commented Mar 20, 2020

Think what ever is under eng/* should be submitted to arcade project (and than that's roll in automatically)
cc: @safern @ViktorHofer

@davidsh
Copy link
Contributor

davidsh commented Mar 20, 2020

Think what ever is under eng/* should be submitted to arcade project (and than that's roll in automatically)

The stress pipeline (and the enterprise-linux pipeline) don't run in Helix or use Arcade at all. They simply define a new pipeline directly and run it either manually or triggered by pushes/commits to the branch.

@wfurt
Copy link
Member

wfurt commented Mar 20, 2020

yes, I understand that. But lot of the eng/build files live in arcade repo and are mirrored to runtime. But it seems like docker is not one one them.

@safern
Copy link
Member

safern commented Mar 20, 2020

What needs to go into arcade is everything under eng/common not under eng.

Copy link
Contributor

@davidsh davidsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

I would recommend you manually invoke the stress tests pipelines in this PR to validate it. Currently the stress tests aren't automatically invoked for every PR.

@alnikola
Copy link
Contributor Author

/azp list

@alnikola
Copy link
Contributor Author

/azp run runtime-libraries stress-http

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@alnikola
Copy link
Contributor Author

/azp run runtime-libraries stress-ssl

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@alnikola
Copy link
Contributor Author

/azp run runtime-libraries stress-http

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@alnikola
Copy link
Contributor Author

/azp run runtime-libraries stress-ssl

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@alnikola alnikola merged commit 5d874be into dotnet:master Mar 24, 2020
@alnikola alnikola deleted the alnikola/stress-private-aspnet-in-docker branch March 24, 2020 16:35
@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants