Mark Wilkie

> Known issues should look for builds in dnceng/internal as well as dnceng/public and dnceng-public/public. This is true- is that problamatic? > I think it makes sense that it doesn't...

One option could be that if the test fails in some small number (3???) configurations or less, then the configurations are shown. However, if not - then perhaps a header...

I still like the idea of collapsible sections with which ones being expanded by default being "smart". If folks are still wanting summary, then we can go from there. The...

That's an interesting idea @ChadNedzlek. Maybe we float this on the teams channel and a few known suspects?

yea, I think the original thinking/goal was to make it clear that something is dreadfully wrong and is affecting most builds. Perhaps it's time to determine the right "bar" for...

Here's some docs @tlakollo as it sounds like you're interested. https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssues.md

cc/ @karelz for visibility Also, thoughts @garath on how we could proactively report/alert on this in the future?

> I do think we probably need a little help section/icon that links to some helpful page that can answer questions though. Yep, this keeps coming up. Also, I like...

Another one to make sure we consider in triage @ilyas1974 and @garath

Thoughts about where this might live @missymessa. It's probably not a priority for the current validation epic, but do you see a need to open a new one?