Skip to content
.NET

fix wrong number parsing #21

Sign in to view logs

fix wrong number parsing

fix wrong number parsing #21

Triggered via push August 9, 2025 17:20
@jogibear9988jogibear9988
pushed 5cc963b
master
Status Success
Total duration 2m 28s
Artifacts –

dotnet.yml

on: push
build
2m 24s
build
Fit to window
Zoom out
Zoom in

Annotations

10 warnings and 1 notice
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build: Source/SVGImage/SVG/Shapes/TextString.cs#L8
XML comment is not placed on a valid language element
build
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677