-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
H/3 stress #55098
H/3 stress #55098
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsSpin off #54762
|
The stress tests have run. So the pipelines work, docker files are OK, etc.
This might be a recent change in kestrel or our client that breaks it since I'm updating here to 6.0 nightly. @antonfirsov Do you know anything about it? cc: @CarnaViire |
So the error reproduces locally without docker. It happened sometime between 6.0 preview 4 and preview 6. I tested it firstly on preview 4 - no error, downloaded preview 6 and retested and it happens. |
H/2 issue filed: #55261 |
@@ -1,4 +1,4 @@ | |||
ARG SDK_BASE_IMAGE=mcr.microsoft.com/dotnet/nightly/sdk:5.0-buster-slim | |||
ARG SDK_BASE_IMAGE=mcr.microsoft.com/dotnet/nightly/sdk:6.0-bullseye-slim |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this? Seems like buster is still latest stable...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No we don't. I didn't realize it's "testing" and not "stable". I just took the newest without checking. I'll revert it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll need the bullseye after all. Seems like buster doesn't have current 6.0 preview SDK...
<configuration> | ||
<packageSources> | ||
<!-- Add public nuget feed. --> | ||
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this default? I don't mind to be explicit but I'm wondering if we need it in case we do not need custom feeds
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not if run from runtime repo, ours explicitly removes nuget.org: https://github.com/dotnet/runtime/blob/main/NuGet.config
So it all works in docker, where it's isolated, but when you ran it locally from S.N.Http/tests/... it failed due to one dependency coming from the public feed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
generally looks ok to me.
b057c44
to
ca9ab3b
Compare
@@ -47,6 +47,14 @@ jobs: | |||
name: buildStress | |||
displayName: Build HttpStress | |||
|
|||
- bash: | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll see, but on Linux we should be now able to run stress tests.
@@ -7,6 +7,18 @@ RUN echo "DOTNET_VERSION="$DOTNET_VERSION | |||
WORKDIR /app | |||
COPY . . | |||
|
|||
# Pulling the msquic Debian package from msquic-ci public pipeline and from a hardcoded build. | |||
# Note that this is a temporary solution until we have properly published Linux packages. | |||
# Also note that in order to update to a newer msquic build, you have update this link. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this link already contain changes needed for #55291? If not, can we update it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it does contain them.
/azp run runtime-libraries stress-http |
/azp run runtime-libraries stress-ssl |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
Stress tests on Linux are running H/3 🥳 |
Seeing 10s thousands of |
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
d2ef2ad
to
84f63a4
Compare
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
Looks good now: https://dev.azure.com/dnceng/public/_build/results?buildId=1227406&view=results CI errors are unrelated, merging. |
Spin off #54762
Fixes #40389