Skip to content

Fix string comparison in PChecker runtime (#919) #3070

Fix string comparison in PChecker runtime (#919)

Fix string comparison in PChecker runtime (#919) #3070

Triggered via push December 12, 2025 04:58
Status Success
Total duration 12m 54s
Artifacts

windowsci.yml

on: push
Build-And-Test-Windows
12m 51s
Build-And-Test-Windows
Fit to window
Zoom out
Zoom in

Annotations

14 warnings
Build-And-Test-Windows
The type name 'y' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'a' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'x' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'y' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'a' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'x' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'a' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'a' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'ev' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'ev' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows: Tst/UnitTests/TypeCheckingUtilsTest.cs#L3
The using directive for 'NUnit.Framework' appeared previously in this namespace
Build-And-Test-Windows: Tst/UnitTests/TypeCheckingUtilsTest.cs#L3
The using directive for 'NUnit.Framework' appeared previously in this namespace