-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Test failure: Microsoft.Extensions.Hosting.UseWindowsServiceTests.CanCreateService #103548
Comments
Tagging subscribers to this area: @dotnet/area-system-serviceprocess |
Failed in: runtime-coreclr libraries-jitstress 20240618.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20240627.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress2-jitstressregs 20240629.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20240701.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20240703.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20240714.1 Failed tests:
Error message:
Stack trace:
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
cc @dotnet/jit-contrib. |
This does not look like a codegen issue, e.g. https://dev.azure.com/dnceng-public/public/_build/results?buildId=735208&view=results from the table above has a failure in the regular runtime pipeline. |
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
Tagging subscribers to this area: @dotnet/area-system-serviceprocess |
Failed in: runtime-coreclr libraries-jitstress 20240715.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20240717.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstressregs 20240728.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20240803.1 Failed tests:
Error message:
Stack trace:
|
@ericstj, I noticed this test failure was put into future with no comments indicating the reason behind the milestone move, nor if the test was disabled. Would you please provide some clarity around that? |
Failed in: runtime-coreclr libraries-jitstress2-jitstressregs 20240810.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20240819.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20240822.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-pgo 20240823.1 Failed tests:
Error message:
Stack trace:
|
It was moved into future because at the time it had 0 recent hit counts. Odd that there have been new hits mentioned here, but no updates to the count table. Probably because it's only failing in these other pipelines which don't get build-analysis. This test is trying to start a windows service and gives it 30 seconds to start. It's not expected to fail this often: runtime/src/libraries/Microsoft.Extensions.Hosting.WindowsServices/tests/WindowsServiceTester.cs Line 51 in 4b9e2f4
I could see how it might fail occasionally if the machine was very slow, or overly taxed with work. I wonder if there's something about the environment of these tests that's causing process startup to take much longer (or even crash)? @mikelle-rogers @v-wenyuxu - is this a 100% failure for the optional build pipelines mentioned, or is it still passing some of the time? |
Hi @ericstj, it is failing in regular runtime pipeline and various JIT optional pipelines (jitstress, jitstress2, libraries-pgo). Can you please disable the test until you get back to the issue? |
We are getting close to the product release, so I want to make sure that our optional pipelines are all green. |
Failed in: runtime-coreclr libraries-jitstress 20240827.1 Failed tests:
Error message:
Stack trace:
|
Backporting to 9.0 as well #107109 |
Failed in: runtime-coreclr libraries-jitstress 20240616.1
Failed tests:
Error message:
Stack trace:
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=709265
Error message validated:
[The operation requested for service 'CanCreateService' has not been completed within the specified time interval.
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/18/2024 12:11:43 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: