-
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
outerloop legs failing to detect dotnet
#76755
Comments
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsOriginal issue was opened in dotnet/arcade: dotnet/arcade#11185 Many outerloop legs fail with this message when attempting to run unit tests:
The investigation found that this may have been caused by a runtime change that happened between these two runs (from 8/2 to 8/3): pr/public/dotnet/runtime/refs/pull/73300/merge Kusto QueryJobs
| where QueueName == "osx.1200.amd64.open"
| extend Propz = parse_json(Properties)
| where Propz["DefinitionName"] == "runtime-libraries-coreclr outerloop"
| where Propz["System.PhaseName"] == "libraries_build_OSX_x64_Debug"
| order by Finished desc The main suspect PR is one that seeked to remove the host packages conditionally and was merged at a time between the above two PRs likely merge commits: https://github.com/dotnet/runtime/pull/73095/files We need to confirm this issue caused the regression and get it fixed.
|
#73095 made it so that the This is the portion of the change that handled it in PR/innerloop test runs: runtime/eng/pipelines/libraries/run-test-job.yml Lines 91 to 93 in cb6e5e7
It seems outerloop doesn't go through that. My guess would be that |
There was a PR I had a while back: #74468. Viktor said he wanted to do this differently, probably merging outer and inner loop as you point out. |
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsOriginal issue was opened in dotnet/arcade: dotnet/arcade#11185 Many outerloop legs fail with this message when attempting to run unit tests:
The investigation found that this may have been caused by a runtime change that happened between these two runs (from 8/2 to 8/3): pr/public/dotnet/runtime/refs/pull/73300/merge Kusto QueryJobs
| where QueueName == "osx.1200.amd64.open"
| extend Propz = parse_json(Properties)
| where Propz["DefinitionName"] == "runtime-libraries-coreclr outerloop"
| where Propz["System.PhaseName"] == "libraries_build_OSX_x64_Debug"
| order by Finished desc The main suspect PR is one that seeked to remove the host packages conditionally and was merged at a time between the above two PRs likely merge commits: https://github.com/dotnet/runtime/pull/73095/files We need to confirm this issue caused the regression and get it fixed.
|
fwiw the badssl readme says "badssl.com is meant for manual testing of security UI in web clients." |
Because of this, outerloop is completely unreliable now. Note that only about 12% of the cases are passing. This is very unfortunate eg. for the networking libs, where a significant portion of the tests live in outerloop, and we prefer to run them on every PR touching relevant functionality. |
I disabled the outerloop pipelines months ago and they weren't supposed to be running at all (because they are fundamentally broken). Presumably they were unintentionally re-enabled when the migration to dnceng-public.visualstudio.com happened. I also just noticed that the outerloop mono pipeline doesn't exist anymore, it was probably lost during the migration. I'm attempting to fix the broken outerloop pipeline in #79652 but I can't give any guarantees as most of the related code was written by someone else. |
* Fix libraries outerloop pipelines Fixes #76755
Original issue was opened in dotnet/arcade: dotnet/arcade#11185
Many outerloop legs fail with this message when attempting to run unit tests:
The investigation found that this may have been caused by a runtime change that happened between these two runs (from 8/2 to 8/3):
pr/public/dotnet/runtime/refs/pull/73300/merge
pr/public/dotnet/runtime/refs/pull/73020/merge
Kusto Query
The main suspect PR is one that seeked to remove the host packages conditionally and was merged at a time between the above two PRs likely merge commits: https://github.com/dotnet/runtime/pull/73095/files
We need to confirm this issue caused the regression and get it fixed.
The text was updated successfully, but these errors were encountered: