Youssef Victor

> One such stack trace consists of 4572 lines, because every frame is listed. I've never seen that before, it usually lists a dozen of lines ending this "repeated x...

> Looking at the dump files themselves, I don't see any reference to the code causing the stack overflow in VS. Tried Run Diagnostic Analysis, Crash, which reports no issues....

> The workaround fails with the following error: > > ``` > Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 7 > ``` > > File contents at https://github.com/SteeltoeOSS/Steeltoe/blob/update-xunit-mtp2/mtp-test-entitlements.plist....

@nohwnd I think the question here is that the [dump](https://github.com/SteeltoeOSS/Steeltoe/actions/runs/19900295468?pr=1626) doesn't point out to the recursion that's causing the crash here. This also feels more like a runtime question, as...

@bart-vmware In MTP we have `--crashdump-type` which defaults to `Full`. In VSTest that there is a similar option which defaults to `Mini`. That's likely why you see larger dump files...

There is no `--tl`, but there is `-tl:off`. It might have an impact on the output, but I never looked closely at what exactly it affects. @nohwnd @mariam-abdulla Do you...

I'm not sure this is the best design. The given scenario probably needs a different approach. Marking as Needs: Design for now. We would also need to get more user...

We need to also think about this for CI scenarios. For example, if you publish TRX files to AzDO, how can that information be surfaced correctly there so that the...

I think we could have a heuristic here specific to multi-line diffing, similar to how the diffing from Roslyn testing library works. I think Roslyn testing uses https://github.com/mmanela/diffplex. I'm not...

Related: https://github.com/microsoft/testfx/issues/6771