Skip to content

Conversation

nohwnd
Copy link
Member

@nohwnd nohwnd commented Nov 20, 2023

Use settings from xslt which will set the output mode to HTML and will emit <div></div> instead of <div /> which is not a valid HTML syntax (but is valid XML syntax).

Fix #4754

@Evangelink Evangelink enabled auto-merge (squash) November 20, 2023 10:27
@nohwnd
Copy link
Member Author

nohwnd commented Nov 20, 2023

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Evangelink
Copy link
Member

@nohwnd looks like there is a test to fix:

Failed HtmlLoggerWithFriendlyNameContainsExpectedContent (Row: 0, Runner = netcoreapp3.1, TargetFramework = net462, InProcess) [3 s]
  Error Message:
   Test method Microsoft.TestPlatform.AcceptanceTests.LoggerTests.HtmlLoggerWithFriendlyNameContainsExpectedContent threw exception: 
System.Xml.XmlException: The 'br' start tag on line 5 position 83 does not match the end tag of 'div'. Line 5, position 88.
  Stack Trace:
      at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
   at System.Xml.XmlTextReaderImpl.ThrowTagMismatch(NodeData startTag)
   at System.Xml.XmlTextReaderImpl.ParseEndElement()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
   at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.Load(String filename)
   at Microsoft.TestPlatform.AcceptanceTests.LoggerTests.HtmlLoggerWithFriendlyNameContainsExpectedContent(RunnerInfo runnerInfo) in /_/test/Microsoft.TestPlatform.Acceptance.IntegrationTests/LoggerTests.cs:line 73

This was referenced Oct 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The HTML report has visual glitches (stairs effect) with the .NET 8 SDK

3 participants