Turn on disabled tracing tests #56507
Conversation
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
|
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-libraries-coreclr outerloop |
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp list |
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
josalem
changed the title
josalem
added
disabled-test
|
Tagging subscribers to this area: @tommcdon Issue Details
I've run the outer loop tests a few times and I haven't seen the listed tests fail. A good number of these tests are simply marked as "needs triage" with no associated GitHub issue. I'm more than happy to turn these back off, but I am hoping to have them on for .net6 in the hopes that we can catch product issues in an LTS branch for servicing over time.
|
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
All failures in outerloop appear to be infrastructure (xunit "list modified while enumerating" issue) or R2R failures. I've yet to see these tests fail in outerloop runs in this PR. |
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Remaining failures are #55657 |
ghost
locked as resolved and limited conversation to collaborators
Removing all exclusions for tracing/* tests to find which are still failing in CI and which we might be able to turn back on. Not all of them have an associated issue unfortunately, and some of the issues for these test failures have links to builds that have long since been culled by AzDO.This PR isn't intended to be merged.I've run the outer loop tests a few times and I haven't seen the listed tests fail. A good number of these tests are simply marked as "needs triage" with no associated GitHub issue. I'm more than happy to turn these back off, but I am hoping to have them on for .net6 in the hopes that we can catch product issues in an LTS branch for servicing over time.