Apply suggestions from code review
Build Analysis / Build Analysis
failed
Jul 26, 2024 in 0s
.NET Result Analysis
Details
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
🕒 The following pipeline(s) will be analyzed once they finish
Known Repository Errors
Build Failures
runtime-dev-innerloop / Build / linux-x64 debug Libraries_AllConfigurations / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/libraries/System.IO.Compression.Brotli/src/System/IO/Compression/enc/BrotliStream.Compress.cs(19,107): error CS1570: XML comment has badly formed XML -- 'End tag was not expected at this location.'
-
❌src/libraries/System.IO.Compression.Brotli/src/System/IO/Compression/enc/BrotliStream.Compress.cs(26,107): error CS1570: XML comment has badly formed XML -- 'End tag was not expected at this location.'
-
❌src/libraries/System.IO.Compression.Brotli/src/System/IO/Compression/enc/BrotliStream.Compress.cs(38,148): error CS1570: XML comment has badly formed XML -- 'End tag was not expected at this location.'
Was this helpful?
Loading